Repository compromise via token-bearing workflow artifact
Published May 6, 2025 · Updated May 6, 2025
Sensitive-information exposure in PHP.GT Dom before 4.1.8 allows remote attackers to obtain a workflow GITHUB_TOKEN from a build artifact. The ci.yml archive command packages the current checkout, including .git/config where GitHub places the token, and upload-artifact publishes that archive. Exploitation requires downloading the artifact during the short workflow run; the token then permits malicious pushes or release-tag rewrites within its assigned permissions.
Summary
What happened
Sensitive-information exposure in PHP.GT Dom before 4.1.8 allows remote attackers to obtain a workflow GITHUB_TOKEN from a build artifact. The ci.yml archive command packages the current checkout, including .git/config where GitHub places the token, and upload-artifact publishes that archive. Exploitation requires downloading the artifact during the short workflow run; the token then permits malicious pushes or release-tag rewrites within its assigned permissions.
The record
- CVE
- CVE-2025-46820
- Published
- May 6, 2025
- Updated
- May 6, 2025
- Vendor
- PHP.GT
- Product
- Dom
- Classifications
- CWE-522, CWE-200, CWE-312, CWE-538, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2025CVE publishedPublication date reported by the CVE source.
- May 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.1.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-cwj7-6v67-2cm4 artifact-token proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo