CVE-2025-32953 json
z80pack Vulnerable to Exposure of the GITHUB_TOKEN in Workflow Run Artifact
published 2025-04-18 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-11894
- cvss
- 8.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
z80pack is a mature emulator of multiple platforms with 8080 and Z80 CPU. In version 1.38 and prior, the `makefile-ubuntu.yml` workflow file uses `actions/upload-artifact@v4` to upload the `z80pack-ubuntu` artifact. This artifact is a zip of the current directory, which includes the automatically generated `.git/config` file containing the run's GITHUB_TOKEN. Seeing as the artifact can be downloaded prior to the end of the workflow, there is a few seconds where an attacker can extract the token from the artifact and use it with the Github API to push malicious code or rewrite release commits in your repository. This issue has been fixed in commit bd95916.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H |
Affected products
- udo-munk z80pack
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
- github.com /udo-munk/z80pack/commit/1e06c2fe498ca772002b5c4f6f9e3085061e47da
- github.com /udo-munk/z80pack/commit/836c2e37b54f86bb4bed9e1406b67e52aa52308d
- github.com /udo-munk/z80pack/commit/95535987d690bd20849fbf143f267283f0e2db91
- github.com /udo-munk/z80pack/commit/bd9591615ae7b1e6229aa60a485447441c4a0c15
- github.com /udo-munk/z80pack/security/advisories/GHSA-gpjj-f76m-9x3q
Sources
- CVE List CVE-2025-32953
- NVD CVE-2025-32953
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.