CVE-2025-27154: Spotipy is a lightweight Python library for the Spotify Web API

Q: How do I fix CVE-2025-27154?

spotipy: upgrade to 2.25.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-27154 being exploited?

CVE-2025-27154 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-27154 affect?

CVE-2025-27154 affects spotipy. Severity is critical (CVSS 9.8). 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

Q: How urgent is CVE-2025-27154?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-27154 is a critical-severity flaw (CVSS 9.8) affecting spotipy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 anoth

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-276
Published	2025-02-27
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: spotipy project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-27 14:15 UTCPublished CVE record published
2026-06-17 09:03 UTCUpdated Record last modified

spotipy project spotipy UPGRADE

Affected: < 2.25.1

Fixed in: 2.25.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy spotipy || rpm -q spotipy || spotipy --version

2. UPGRADE to 2.25.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spotipy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spotipy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-27154?

spotipy: upgrade to 2.25.1. Exact commands for each OS are on this page.

Is CVE-2025-27154 being exploited?

CVE-2025-27154 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-27154 affect?

CVE-2025-27154 affects spotipy. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2025-27154?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

References

← Back to latest CVEs