CVE-2025-54430 dedupe is vulnerable to secret exfiltration via `issue_comment`
Attackers can execute arbitrary code via GitHub Actions workflow injection, leading to GITHUB_TOKEN exfiltration and potential repository takeover.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-54430?
CVE-2025-54430 is a critical command injection vulnerability in dedupeio dedupe, published on 30 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
dedupe is a python library that uses machine learning to perform fuzzy matching, deduplication and entity resolution quickly on structured data. Before commit 3f61e79, a critical severity vulnerability has been identified within the .github/workflows/benchmark-bot.yml workflow, where a issue_comment can be triggered using the @benchmark body. This workflow is susceptible to exploitation as it checkout the ${{ github.event.issue.number }}, which correspond to the branch of the PR manipulated by potentially malicious actors, and where untrusted code may be executed. Running untrusted code may lead to the exfiltration of GITHUB_TOKEN, which in this workflow has write permissions on most of the scopes - in particular the contents one - and could lead to potential repository takeover. This is fixed by commit 3f61e79.
Weakness: CWE-78
Which versions are affected by CVE-2025-54430?
How do I fix CVE-2025-54430?
No fix has been published for CVE-2025-54430 yet. Limit exposure of the affected software until one is available.
Upgrade, and pass arguments to programs as a list instead of through a shell. More about Command injection.
Is CVE-2025-54430 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54430 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-wrg3-xqw8-m85p.