First published: Tue May 06 2025(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
phpgt Dom | <4.1.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-46820 is considered a security vulnerability that exposes sensitive information, specifically the GITHUB_TOKEN.
To fix CVE-2025-46820, update phpgt/Dom to version 4.1.8 or later.
Versions of phpgt/Dom prior to 4.1.8 are affected by CVE-2025-46820.
CVE-2025-46820 exposes the GITHUB_TOKEN in the Dom workflow run artifact.
CVE-2025-46820 occurs due to the use of actions/upload-artifact@v4 in the ci.yml workflow file.