CVE-2025-47928 Spotipy repo vulnerable to secrets exfiltration via `pull_request_target`
Attackers can exfiltrate GitHub secrets and tokens via pull_request_target workflow, enabling repository takeover in the Spotipy library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-47928?
CVE-2025-47928 is a critical vulnerability in spotipy-dev spotipy, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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 Actions is a major security concern—especially in public repositories—because it executes untrusted code from a PR, but with the context of the base repository, including access to its secrets. Commit 9dfb7177b8d7bb98a5a6014f8e6436812a47576f reverted the change that caused the issue.
Weakness: CWE-488
Which versions are affected by CVE-2025-47928?
How do I fix CVE-2025-47928?
No fix has been published for CVE-2025-47928 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-47928 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47928 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-h25v-8c87-rvm8, UBUNTU-CVE-2025-47928.