p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in spotipy

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für spotipy: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3

  1. CVE-2025-66040

    Niedrig · CVSS 3.6EPSS 0,17%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert
  2. CVE-2025-47928

    Kritisch · CVSS 9.1EPSS 0,63%Keine Korrektur veröffentlicht

    Spotipy repo vulnerable to secrets exfiltration via `pull_request_target`

    Spotipy is a Python library for the Spotify Web API. As of commit 4f5759dbfb4506c7b6280572a4db1aabc1ac778d, using `pull_request_target` on `.github/workflows/integration_tests.yml` followed by the checking out the head.sha of a forked PR can be exploited by attackers, since untrusted code can be executed having full access to secrets (from the base repo). By exploiting the vulnerability is possible to exfiltrate `GITHUB_TOKEN` and secrets `SPOTIPY_CLIENT_ID`, `SPOTIPY_CLIENT_SECRET`. In particular `GITHUB_TOKEN` which can be used to completely overtake the repo since the token has content write privileges. The `pull_request_target` in GitHub

    Veröffentlicht Aktualisiert
  3. CVE-2025-27154

    Hoch · CVSS 8.4EPSS 0,61%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →