{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54430 exists.","fix":"No fix has been published for CVE-2025-54430 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-54430 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54430 exists.\n\nAffected product: dedupeio dedupe. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-54430/ (Markdown: https://insights.sbomify.com/CVE-2025-54430/index.md)","id":"CVE-2025-54430","markdown":"https://insights.sbomify.com/CVE-2025-54430/index.md","name":"CVE-2025-54430","record":{"aliases":["GHSA-wrg3-xqw8-m85p"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Python deduplication library","requires_auth":"none","summary":"Attackers can execute arbitrary code via GitHub Actions workflow injection, leading to GITHUB_TOKEN exfiltration and potential repository takeover.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-04T07:51:12Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-ba981941f0","stars":0,"title":"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."}],"tier":"weaponised"},"has_fix":false,"headline":"dedupe is vulnerable to secret exfiltration via `issue_comment`","id":"CVE-2025-54430","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE is a duplicate of another CVE.","id":"CVE-2025-54432"},"packages":[],"prev":{"headline":"Polkadot Frontier's constructing smart contract can bypass precompile address bounding","id":"CVE-2025-54429"},"products":["dedupe"],"published":"2025-07-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-30","vendors":["dedupeio"]},"summary":"Attackers can execute arbitrary code via GitHub Actions workflow injection, leading to GITHUB_TOKEN exfiltration and potential repository takeover.","url":"https://insights.sbomify.com/CVE-2025-54430/"}