# 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.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-h25v-8c87-rvm8, UBUNTU-CVE-2025-47928

## 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 (Exposure of Data Element to Wrong Session)

## 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:

- Authorized lab reproduction of CVE-2025-47928 (spotipy-dev/spotipy pull_request_target secrets exfiltration) — snapshot at vulnerable commit 4f5759d (github_poc): https://github.com/pvharmo2/gha-lab-2f775f277c

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47928 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47928 exists.

Affected product: spotipy-dev spotipy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47928/ (Markdown: https://insights.sbomify.com/CVE-2025-47928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47928
- OSV: https://osv.dev/vulnerability/CVE-2025-47928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47928/
Summaries are generated and may contain mistakes; the official description above is the record.