{"metadata": {"vulnerability": "GHSA-H25V-8C87-RVM8", "count": 7, "kinds": {"milestone": 2, "sighting": 1, "kev": 0, "other": 4}, "linked_omitted": 0}, "data": [{"timestamp": "2025-05-14T10:32:43.528Z", "date_only": false, "value": "2025-05-14T10:32:43.528Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5 \u00b7 CVE-2025-47928", "record": "CVE-2025-47928", "field": "cveMetadata.dateReserved", "linked_record": true}, {"timestamp": "2025-05-15T20:09:48.326Z", "date_only": false, "value": "2025-05-15T20:09:48.326Z", "kind": "milestone", "label": "Published", "source": "cvelistv5 \u00b7 CVE-2025-47928", "record": "CVE-2025-47928", "field": "cveMetadata.datePublished", "linked_record": true}, {"timestamp": "2025-05-15T20:09:48.326Z", "date_only": false, "value": "2025-05-15T20:09:48.326Z", "kind": "other", "label": "Updated", "source": "cvelistv5 \u00b7 CVE-2025-47928 / GitHub_M", "record": "CVE-2025-47928", "field": "containers.cna.providerMetadata.dateUpdated", "linked_record": true}, {"timestamp": "2025-05-15T20:17:02.996Z", "date_only": false, "value": "2025-05-15T20:17:02.996955Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 \u00b7 CVE-2025-47928 / CISA-ADP", "record": "CVE-2025-47928", "field": "containers.adp.0.metrics.0.other.content.timestamp", "linked_record": true}, {"timestamp": "2025-05-15T20:18:00.369Z", "date_only": false, "value": "2025-05-15T20:18:00.369Z", "kind": "other", "label": "Updated", "source": "cvelistv5 \u00b7 CVE-2025-47928", "record": "CVE-2025-47928", "field": "cveMetadata.dateUpdated", "linked_record": true}, {"timestamp": "2025-05-15T20:18:00.369Z", "date_only": false, "value": "2025-05-15T20:18:00.369Z", "kind": "other", "label": "Updated", "source": "cvelistv5 \u00b7 CVE-2025-47928 / CISA-ADP", "record": "CVE-2025-47928", "field": "containers.adp.0.providerMetadata.dateUpdated", "linked_record": true}, {"timestamp": "2025-05-15T20:33:31Z", "date_only": false, "value": "2025-05-15T20:33:31.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16552", "record": "GHSA-H25V-8C87-RVM8", "field": "creation_timestamp", "uuid": "4d74fcea-62fa-4dcf-9021-f167b9706760", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-47928\n\ud83d\udd25 CVSS Score: 9.1 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 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\u2014especially in public repositories\u2014because 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.\n\ud83d\udccf Published: 2025-05-15T20:09:48.326Z\n\ud83d\udccf Modified: 2025-05-15T20:18:00.369Z\n\ud83d\udd17 References:\n1. https://github.com/spotipy-dev/spotipy/security/advisories/GHSA-h25v-8c87-rvm8\n2. https://github.com/spotipy-dev/spotipy/commit/4f5759dbfb4506c7b6280572a4db1aabc1ac778d\n3. https://github.com/spotipy-dev/spotipy/commit/9dfb7177b8d7bb98a5a6014f8e6436812a47576f", "url": "https://t.me/DarkWebInformer_CVEAlerts/16552", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}], "metrics": {"as_of": "2026-11-22T22:03:43.608Z", "anchors": {"origin": null, "discovery": null, "report": null, "acknowledgement": null, "disclosure": null, "exploit_publication": {"timestamp": "2025-05-15T20:33:31Z", "date_only": false, "value": "2025-05-15T20:33:31.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16552", "record": "GHSA-H25V-8C87-RVM8", "field": "creation_timestamp", "uuid": "4d74fcea-62fa-4dcf-9021-f167b9706760", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-47928\n\ud83d\udd25 CVSS Score: 9.1 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 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\u2014especially in public repositories\u2014because 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.\n\ud83d\udccf Published: 2025-05-15T20:09:48.326Z\n\ud83d\udccf Modified: 2025-05-15T20:18:00.369Z\n\ud83d\udd17 References:\n1. https://github.com/spotipy-dev/spotipy/security/advisories/GHSA-h25v-8c87-rvm8\n2. https://github.com/spotipy-dev/spotipy/commit/4f5759dbfb4506c7b6280572a4db1aabc1ac778d\n3. https://github.com/spotipy-dev/spotipy/commit/9dfb7177b8d7bb98a5a6014f8e6436812a47576f", "url": "https://t.me/DarkWebInformer_CVEAlerts/16552", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["start", "end"]}, "disclosure_to_exploit": {"available": false, "missing": ["start", "end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["start"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["start", "end"]}, "time_unpatched": {"available": false, "missing": ["start"]}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": true, "seconds": 48043812.608797, "hours": 13345.503502443611, "days": 556.0626459351505, "min_seconds": 48043812.608797, "max_seconds": 48043812.608797, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2025-05-15T20:33:31Z", "date_only": false, "value": "2025-05-15T20:33:31.000000Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16552", "record": "GHSA-H25V-8C87-RVM8", "field": "creation_timestamp", "uuid": "4d74fcea-62fa-4dcf-9021-f167b9706760", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-47928\n\ud83d\udd25 CVSS Score: 9.1 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 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\u2014especially in public repositories\u2014because 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.\n\ud83d\udccf Published: 2025-05-15T20:09:48.326Z\n\ud83d\udccf Modified: 2025-05-15T20:18:00.369Z\n\ud83d\udd17 References:\n1. https://github.com/spotipy-dev/spotipy/security/advisories/GHSA-h25v-8c87-rvm8\n2. https://github.com/spotipy-dev/spotipy/commit/4f5759dbfb4506c7b6280572a4db1aabc1ac778d\n3. https://github.com/spotipy-dev/spotipy/commit/9dfb7177b8d7bb98a5a6014f8e6436812a47576f", "url": "https://t.me/DarkWebInformer_CVEAlerts/16552", "metric_role": "exploit_publication", "metric_basis": "sighting_report"}, "end": {"timestamp": "2026-11-22T22:03:43.608Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}}}
