{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47928 exists.","fix":"No fix has been published for CVE-2025-47928 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-47928 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47928 exists.\n\nAffected product: spotipy-dev spotipy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47928/ (Markdown: https://insights.sbomify.com/CVE-2025-47928/index.md)","id":"CVE-2025-47928","markdown":"https://insights.sbomify.com/CVE-2025-47928/index.md","name":"CVE-2025-47928","record":{"aliases":["GHSA-h25v-8c87-rvm8","UBUNTU-CVE-2025-47928"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Python Spotify library","requires_auth":"none","summary":"Attackers can exfiltrate GitHub secrets and tokens via pull_request_target workflow, enabling repository takeover in the Spotipy library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-04T01:38:40Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-2f775f277c","stars":0,"title":"Authorized lab reproduction of CVE-2025-47928 (spotipy-dev/spotipy pull_request_target secrets exfiltration) — snapshot at vulnerable commit 4f5759d"}],"tier":"weaponised"},"has_fix":false,"headline":"Spotipy repo vulnerable to secrets exfiltration via `pull_request_target`","id":"CVE-2025-47928","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"DumbDrop vulnerable to DOM XSS via file upload","id":"CVE-2025-47929"},"packages":[],"prev":{"headline":"Use after free in mbedtls","id":"CVE-2025-47917"},"products":["spotipy"],"published":"2025-05-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-15","vendors":["spotipy-dev"]},"summary":"Attackers can exfiltrate GitHub secrets and tokens via pull_request_target workflow, enabling repository takeover in the Spotipy library.","url":"https://insights.sbomify.com/CVE-2025-47928/"}