critical CVSS 9.8 EPSS 0.59%

CVE-2025-27154·Python vulnerability

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.

Severity
critical
Software
Python
Fixed in
2.25.1
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.59% — higher than 44% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2025-27154 scores 9.8 on CVSS, so a successful attack would be serious — but at 0.59%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 2.25.1

Fixed in: 2.25.1

How to fix this CVE

Update the Spotipy library to version 2.25.1 or later to remediate insecure cache file permissions that expose Spotify authentication tokens. The vulnerability allows other users or processes on the same system to read cached credentials with overly permissive (644) file modes. Upgrade immediately if your application uses Spotipy for Spotify API authentication, as compromised tokens enable attackers to perform administrative actions on linked Spotify accounts.

sudo dnf upgrade python3-spotipy

Defensia detects this vulnerability

How to check if you are affected

  1. Check Spotipy version: pip show spotipy | grep Version
  2. Identify Spotipy cache directory: find ~/.cache -name '*spotipy*' -o find ~/.spotipy -type f 2>/dev/null
  3. Verify cache file permissions: ls -la ~/.cache/spotipy* or ls -la ~/.spotipy* (should show 600 or rw------- after patching, not 644 or rw-r--r--)
  4. Confirm patch applied: pip show spotipy | grep -q '2.25.1' && echo 'Patched' || echo 'Vulnerable'

FAQ

What is CVE-2025-27154?

CVE-2025-27154 is a file permission vulnerability in Spotipy's CacheHandler class that creates authentication token cache files with world-readable permissions (644), allowing local system users to steal and misuse Spotify API credentials.

Is CVE-2025-27154 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, though the risk remains high for multi-user systems.

What versions of Spotipy are affected by CVE-2025-27154?

All versions of Spotipy prior to 2.25.1 are affected; version 2.25.1 and later restrict cache file permissions to 600 (rw-------).

How do I check if my server is vulnerable to CVE-2025-27154?

Run: pip show spotipy | grep Version && stat -c '%a' ~/.spotipy* 2>/dev/null — if the version is below 2.25.1 and file permissions show 644, the system is vulnerable.

Does Defensia detect CVE-2025-27154?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Spotipy is installed on a monitored server, CVE-2025-27154 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-8481CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 contain a critical remote code execution vulnerability in the code validation API endpoint. The POST /api/v1/validate/code endpoint accepts user-supplied Python code and executes it directly using Python's built-in exec() function without sandboxing, input validation, or privilege restrictions, enabling any authenticated user to execute arbitrary system commands with the full privileges of the Langflow server process.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-27154. Free for 1 server.

Get started free