Approved changes feed: RSS · Atom
cpe:2.3:a:dedupeio:dedupe:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Dedupeio (a6e19933-dad4-5bd1-81a4-5457a4a88f68) |
|---|---|
| Product | Dedupe (036a9c25-3c74-57cb-b9d7-e3a546981937) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-54430 |
vulnerable | 2026-06-08 07:33:12.592611 |
dedupe is vulnerable to secret exfiltration via `issue_comment`
CRITICAL (9.1)
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.
Published: 2025-07-30T13:41:59.975Z
Updated: 2025-07-30T13:54:21.105Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.