# CVE-2025-32953: z80pack Vulnerable to Exposure of the GITHUB_TOKEN in Workflow Run Artifact

> Attackers can extract GitHub tokens from build artifacts to push malicious code or rewrite repository history in the z80pack emulator project.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-gpjj-f76m-9x3q

## What is CVE-2025-32953?

CVE-2025-32953 is a high-severity vulnerability in udo-munk z80pack, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-32953?


## How do I fix CVE-2025-32953?

No fix has been published for CVE-2025-32953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32953 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32953 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32953 is a high-severity vulnerability in udo-munk z80pack, published on 18 Apr 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-32953 exists.

Affected product: udo-munk z80pack. 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-32953/ (Markdown: https://insights.sbomify.com/CVE-2025-32953/index.md)
```

## Sources

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

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