Advisory record · GHSA-pwhh-q4h6-w599

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

CVSS 8.4 HighEPSS 0.0061 · 50th percentile

Published by the GitHub Advisory Database at 28 Feb 2025, 02:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
spotipyPyPI<2.25.12.25.1
Identifiers
GHSA-pwhh-q4h6-w599 · CVE-2025-27154 · PYSEC-2026-1936
Weakness (CWE)
CWE-276
Published
28 Feb 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spotipy versions before 2.25.1 create the token cache file with world-readable permissions (644) by default. A local user or process on the same machine could read the Spotify auth token from that file and use it to act on the Spotify account, depending on the token's granted scopes. The source gives no fix beyond upgrading. Upgrade to spotipy 2.25.1 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 4.0 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0061, the 50th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.