CVE-2026-61732

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-24. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-86329 (ENISA EUVD) · GHSA-g5f9-3xfg-p9mf (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Decepticon is an autonomous hacking agent for red teams. Versions prior to 1.1.17 wrap web crawl results — the output of agent reconnaissance against target services — into LLM messages without neutralizing ChatML special-token literals. Under the BYOK (Bring Your Own Key) deployment model, users configure their own LLM credentials to any OpenAI-compatible endpoint. Most open-source and self-deployed model providers (vLLM, SGLang, Ollama, LM Studio, text-generation-webui, etc.) do not filter special-token literals from user content in their default configurations. Those literals are parsed into structural role-boundary token IDs, meaning an attacker string planted in a target web page forges a new operator turn the model treats as authoritative, bypassing Decepticon's agent guardrails and resulting in arbitrary command execution inside the Kali Linux sandbox. Version 1.1.17 patches the issue.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
73rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 24, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Role-boundary forgery via ChatML special-token literals in web crawl output composed into LLM context · Advisory · BitterSecurity/Decepticon · GitHub

https://github.com/BitterSecurity/Decepticon/security/advisories/GHSA-g5f9-3xfg-p9mf
GitHub commit

commit 79ee2aaf22f4 (BitterSecurity/Decepticon)

Fix landed in BitterSecurity/Decepticon commit 79ee2aaf22f4 — awaiting tagged release

https://github.com/BitterSecurity/Decepticon/commit/79ee2aaf22f4c36a5b1968f6ca3f8086b6e35b67

Vendor Advisories for CVE-2026-61732(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdecepticon @ 1.1.17 (fixes <= 1.1.16)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
PyPI(3)
PackageVulnerable rangeFix by version rangeDependents
decepticon1.1.0 ... 1.1.9 (17 versions)
  • every version up to 1.1.17: fixed in 1.1.17
—
decepticon-core1.1.10 ... 1.1.9 (15 versions)
  • every version up to 1.1.17: fixed in 1.1.17
—
decepticon-sdk1.1.10 ... 1.1.9 (15 versions)
  • every version up to 1.1.17: fixed in 1.1.17
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 05:22 UTCEG score recompute
  2. 2026-11-02 05:22 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  4. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-11-01 07:41 UTCEG score recompute
  6. 2026-11-01 05:24 UTCEG score recompute
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  8. 2026-10-31 05:25 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-10-30 05:27 UTCEG score recompute
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-10-29 05:29 UTCEG score recompute
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  14. 2026-10-28 05:31 UTCEG score recompute
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-10-27 05:33 UTCEG score recompute
  17. 2026-10-26 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  18. 2026-10-26 01:30 UTCEG score recompute
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  20. 2026-10-25 14:14 UTCEG score recompute
  21. 2026-10-25 01:32 UTCEG score recompute
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  23. 2026-10-24 01:34 UTCEG score recompute
  24. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  25. 2026-10-23 01:36 UTCEG score recompute
Show 59 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  2. 2026-10-22 01:37 UTCEG score recompute
  3. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  4. 2026-10-21 01:39 UTCEG score recompute
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  6. 2026-10-20 01:39 UTCEG score recompute
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  8. 2026-10-19 00:36 UTCEG score recompute
  9. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  10. 2026-10-18 03:25 UTCEG score recompute
  11. 2026-10-18 00:38 UTCEG score recompute
  12. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  13. 2026-10-17 00:38 UTCEG score recompute
  14. 2026-10-16 16:43 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  15. 2026-10-16 00:30 UTCEG score recompute
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  17. 2026-10-14 19:05 UTCEG score recompute
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  20. 2026-10-13 15:32 UTCEG score recompute
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  22. 2026-10-12 15:32 UTCEG score recompute
  23. 2026-10-11 19:34 UTCEG score recompute
  24. 2026-10-11 16:49 UTCEG score recompute
  25. 2026-10-11 14:00 UTCEG score recompute
  26. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  27. 2026-10-10 20:07 UTCEG score recompute
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  29. 2026-10-09 22:06 UTCEG score recompute
  30. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  31. 2026-10-08 21:41 UTCEG score recompute
  32. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  33. 2026-10-08 02:34 UTCEG score recompute
  34. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  35. 2026-10-06 19:30 UTCEG score recompute
  36. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  37. 2026-10-05 21:19 UTCEG score recompute
  38. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  39. 2026-10-05 03:34 UTCEG score recompute
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  41. 2026-10-03 16:15 UTCEG score recompute
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  43. 2026-10-02 18:12 UTCEG score recompute
  44. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  45. 2026-10-01 19:59 UTCEG score recompute
  46. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  47. 2026-09-30 17:33 UTCEG score recompute
  48. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  49. 2026-09-29 19:32 UTCEG score recompute
  50. 2026-09-29 01:49 UTCEG score recompute
  51. 2026-09-28 17:02 UTCEG score recompute
  52. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  53. 2026-09-27 14:26 UTCEG score recompute
  54. 2026-09-26 16:19 UTCEG score recompute
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  56. 2026-09-26 03:02 UTCEG score recompute
  57. 2026-09-24 18:35 UTCEG score recompute
  58. 2026-09-24 17:47 UTCEG score recomputeFirst assessed: 10.0 CRITICAL
  59. 2026-09-24 17:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61732?
CVE-2026-61732 is a critical-severity vulnerability; its CVE record was published on September 24, 2026. Decepticon is an autonomous hacking agent for red teams. Versions prior to 1.1.17 wrap web crawl results — the output of agent reconnaissance against target services — into LLM messages without neutralizing ChatML special-token literals. Under the BYOK (Bring Your Own Key) deployment model, users…
When was the CVE record for CVE-2026-61732 published?
The CVE record for CVE-2026-61732 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61732 actively exploited?
CVE-2026-61732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61732?
CVE-2026-61732 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61732?
A fix for CVE-2026-61732 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61732 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61732

Explore →

Is Your Infrastructure Affected by CVE-2026-61732?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.