# 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.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2025
- **Updated:** 30 Jul 2025
- **Also known as:** GHSA-wrg3-xqw8-m85p

## 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 (Improper Neutralization of Special Elements used in an OS Command)

## 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.

## 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:

- Security-research lab reproducing CVE-2025-54430 (GHSA-wrg3-xqw8-m85p): secrets exfiltration via issue_comment-triggered Benchmark Bot in dedupeio/dedupe. Snapshot of dedupeio/dedupe@54ecfe77d41390da66899596834a2bde3712c966. (github_poc): https://github.com/pvharmo2/gha-lab-ba981941f0

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54430 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54430 exists.

Affected product: dedupeio dedupe. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54430/ (Markdown: https://insights.sbomify.com/CVE-2025-54430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54430
- OSV: https://osv.dev/vulnerability/CVE-2025-54430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54430/
Summaries are generated and may contain mistakes; the official description above is the record.