p PatchFirst

PatchFirst · Latest vulnerabilities

spotipy vulnerabilities

Vulnerabilities published for spotipy in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 3

  1. CVE-2025-66040

    Low · CVSS 3.6EPSS 0.17%Fix available

    Spotipy has a XSS vulnerability in OAuth callback server

    Spotipy is a Python library for the Spotify Web API. Prior to version 2.25.2, there is a cross-site scripting (XSS) vulnerability in the OAuth callback server that allows for JavaScript injection through the unsanitized error parameter. Attackers can execute arbitrary JavaScript in the user's browser during OAuth authentication. This issue has been patched in version 2.25.2.

    • Update to 2.25.2
    Published Updated
  2. CVE-2025-27154

    High · CVSS 8.4EPSS 0.61%Fix available

    Spotipy's cache file, containing spotify auth token, is created with overly broad permissions

    Spotipy is a lightweight Python library for the Spotify Web API. The `CacheHandler` class creates a cache file to store the auth token. Prior to version 2.25.1, the file created has `rw-r--r--` (644) permissions by default, when it could be locked down to `rw-------` (600) permissions. This leads to overly broad exposure of the spotify auth token. If this token can be read by an attacker (another user on the machine, or a process running as another user), it can be used to perform administrative actions on the Spotify account, depending on the scope granted to the token. Version 2.25.1 tightens the cache file permissions.

    • Update to 2.25.1
    Published Updated
  3. CVE-2023-23608

    Low · CVSS 0EPSS 0.66%Fix available

    spotipy Path traversal vulnerability that may lead to type confusion in URI handling code

    Spotipy is a light weight Python library for the Spotify Web API. In versions prior to 2.22.1, if a malicious URI is passed to the library, the library can be tricked into performing an operation on a different API endpoint than intended. The code Spotipy uses to parse URIs and URLs allows an attacker to insert arbitrary characters into the path that is used for API requests. Because it is possible to include "..", an attacker can redirect for example a track lookup via spotifyApi.track() to an arbitrary API endpoint like playlists, but this is possible for other endpoints as well. The impact of this vulnerability depends heavily on what oper

    • Update to 2.22.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →