{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2025-47928","id":"CVE-2025-47928","title":"Spotipy repo vulnerable to secrets exfiltration via `pull_request_target`","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 possibl","descriptionLong":"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.","published":"2025-05-15T20:09:48.326Z","updated":"2026-10-28T02:30:21.586030560Z","reserved":"2025-05-14T10:32:43.528Z","status":"Deferred","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","rating":"critical","source":"GitHub_M"},"metrics":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","rating":"critical","source":"GitHub_M"},{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","rating":"critical","source":"github.com"},{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","rating":"critical","source":"OSV"}],"rating":"critical","products":["spotipy-dev spotipy"],"affectedProducts":[{"vendor":"spotipy-dev","product":"spotipy","defaultStatus":null,"versions":[{"version":"= 4f5759dbfb4506c7b6280572a4db1aabc1ac778d","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-488"],"aliases":["GHSA-h25v-8c87-rvm8"],"references":[{"url":"https://github.com/spotipy-dev/spotipy/security/advisories/GHSA-h25v-8c87-rvm8","tags":["x_refsource_CONFIRM","advisory"]},{"url":"https://github.com/spotipy-dev/spotipy/commit/4f5759dbfb4506c7b6280572a4db1aabc1ac778d","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/spotipy-dev/spotipy/commit/9dfb7177b8d7bb98a5a6014f8e6436812a47576f","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/47xxx/CVE-2025-47928.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-47928","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"yes","technicalImpact":"total"},"epss":0.0064,"epssPercentile":0.51398,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2025-47928","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-47928","ok":true,"note":"Deferred"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2025-47928","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2025-47928","ok":true,"note":"scored 2026-11-18"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}