CVE-2025-46820 phpgt/Dom exposes the GITHUB_TOKEN in Dom workflow run artifact
Attackers can extract GitHub tokens from workflow artifacts to push malicious code or rewrite commits in the repository.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2025-46820?
CVE-2025-46820 is a high-severity vulnerability in phpgt Dom, published on 6 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
phpgt/Dom provides access to modern DOM APIs. Versions of phpgt/Dom prior to 4.1.8 expose the GITHUB_TOKEN in the Dom workflow run artifact. The ci.yml workflow file uses actions/upload-artifact@v4 to upload the build 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. Any downstream user of the repository may be affected, but the token should only be valid for the duration of the workflow run, limiting the time during which exploitation could occur. Version 4.1.8 fixes the issue.
Which versions are affected by CVE-2025-46820?
How do I fix CVE-2025-46820?
No fix has been published for CVE-2025-46820 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-46820 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46820 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-cwj7-6v67-2cm4.