Loading vulnerability…
CVE-2025-54430 affects dedupe, a Python library for fuzzy matching, deduplication, and entity resolution. Prior to commit 3f61e79, the repository's .github/workflows/benchmark-bot.yml workflow could be triggered via issue_comment containing the @benchmark body. The workflow then checked out ${{ github.event.issue.number }}, corresponding to the pull request branch, allowing attacker-controlled and untrusted code from a PR to be executed in the GitHub Actions runner context. Because the workflow ran with a GITHUB_TOKEN that had broad write permissions, including contents write access, successful exploitation could result in token exfiltration and subsequent repository compromise. The issue was fixed in commit 3f61e79.
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.