VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

spotipy: vulnerability history, versions and safety

spotipy is a package in the Debian ecosystem. Vulert records 3 vulnerabilities for it across 1 release, from Feb 2025 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded U3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 27 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all spotipy vulnerabilities

Vulert verdict on spotipy i

Updated on 23 Oct 2026

Careful: one of the 3 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 3 vulnerabilities on record across 1 year, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 1 year · 1 in the last year i
  • Latest disclosure 27 Nov 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for spotipy, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.25.1-1 U1 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for spotipy

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Excessive Token Exposure in Spotipy Package: CVE-2025-27154 9.8 critical 2.25.1-1 27 Feb 2025
Cross-Site Scripting Vulnerability in Spotipy Package 3.6 low No fix published 27 Nov 2025
Critical Security Flaw in Spotipy: Insecure Cache File Permissions Expose Spotify Auth Tokens N/A unrated 2.25.1-1 27 Feb 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About spotipy

Is spotipy safe to use?

Vulert records 3 vulnerabilities for spotipy in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does spotipy have?

3 vulnerabilities are recorded for spotipy in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new spotipy vulnerabilities disclosed?

1 vulnerability was recorded for spotipy in the last 12 months, and the oldest entry in this database dates to 27 Feb 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of spotipy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor spotipy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the spotipy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.