Loading vulnerability…
CVE-2025-46820 affects phpgt/Dom versions prior to 4.1.8. In the project's ci.yml GitHub Actions workflow, actions/upload-artifact@v4 is used to upload a build artifact consisting of a zip of the current working directory. That directory includes the automatically generated .git/config file, which contains the workflow run's GITHUB_TOKEN. Because the artifact is available for download before the workflow completes, an attacker with the ability to access the artifact during that window can extract the token and use it against the GitHub API. The exposed token could then be used to push malicious code or rewrite release commits in the repository. The issue is fixed in version 4.1.8.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.