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
Elevated

Also known asEUVD-2026-86329 (ENISA EUVD) · GHSA-g5f9-3xfg-p9mf (GitHub Security Advisories) · PYSEC-2026-4032 (OSV.dev) · PYSEC-2026-4033 (OSV.dev) · PYSEC-2026-4034 (OSV.dev)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
74th
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-12). 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 Nov 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
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 15× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 118 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 18 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 05:04 UTCEchelonGraph re-scored
  2. 2026-11-13 05:04 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  4. 2026-11-12 05:06 UTCEchelonGraph re-scored
  5. 2026-11-12 05:06 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  7. 2026-11-11 05:07 UTCEchelonGraph re-scored
  8. 2026-11-11 05:07 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  9. 2026-11-10 16:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-11-10 05:09 UTCEchelonGraph re-scored
  11. 2026-11-10 05:09 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-11-09 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-11-09 05:11 UTCEchelonGraph re-scored
  14. 2026-11-09 05:11 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-11-08 05:13 UTCEchelonGraph re-scored
  17. 2026-11-08 05:13 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-11-07 05:14 UTCEchelonGraph re-scored
  20. 2026-11-07 05:14 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  21. 2026-11-06 16:39 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-11-06 14:25 UTCOSV refresh
  23. 2026-11-06 05:16 UTCEchelonGraph re-scored
  24. 2026-11-06 05:16 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  25. 2026-11-05 16:38 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
Show 75 more
  1. 2026-11-05 05:18 UTCEchelonGraph re-scored
  2. 2026-11-05 05:18 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-04 16:36 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  4. 2026-11-04 05:20 UTCEchelonGraph re-scored
  5. 2026-11-04 05:20 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-11-03 16:48 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  7. 2026-11-03 05:21 UTCEchelonGraph re-scored
  8. 2026-11-03 05:21 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  9. 2026-11-02 16:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-11-02 05:22 UTCEchelonGraph re-scored
  11. 2026-11-02 05:22 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-g5f9-3xfg-p9mf · GitHub severity CRITICAL · GitHub CVSS 10.0
  14. 2026-11-01 07:41 UTCEchelonGraph re-scored
  15. 2026-11-01 05:24 UTCEchelonGraph re-scored
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  17. 2026-10-31 05:25 UTCEchelonGraph re-scored
  18. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-10-30 05:27 UTCEchelonGraph re-scored
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  21. 2026-10-29 05:29 UTCEchelonGraph re-scored
  22. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  23. 2026-10-28 05:31 UTCEchelonGraph re-scored
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-10-27 05:33 UTCEchelonGraph re-scored
  26. 2026-10-26 16:32 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  27. 2026-10-26 01:30 UTCEchelonGraph re-scored
  28. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  29. 2026-10-25 14:14 UTCEchelonGraph re-scored
  30. 2026-10-25 01:32 UTCEchelonGraph re-scored
  31. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  32. 2026-10-24 01:34 UTCEchelonGraph re-scored
  33. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  34. 2026-10-23 01:36 UTCEchelonGraph re-scored
  35. 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  36. 2026-10-22 01:37 UTCEchelonGraph re-scored
  37. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  38. 2026-10-21 01:39 UTCEchelonGraph re-scored
  39. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  40. 2026-10-20 01:39 UTCEchelonGraph re-scored
  41. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  42. 2026-10-19 00:36 UTCEchelonGraph re-scored
  43. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  44. 2026-10-18 03:25 UTCEchelonGraph re-scored
  45. 2026-10-18 00:38 UTCEchelonGraph re-scored
  46. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  47. 2026-10-17 00:38 UTCEchelonGraph re-scored
  48. 2026-10-16 16:43 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  49. 2026-10-16 00:30 UTCEchelonGraph re-scored
  50. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  51. 2026-10-14 19:05 UTCEchelonGraph re-scored
  52. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  53. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  54. 2026-10-13 15:32 UTCEchelonGraph re-scored
  55. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  56. 2026-10-12 15:32 UTCEchelonGraph re-scored
  57. 2026-10-11 19:34 UTCEchelonGraph re-scored
  58. 2026-10-11 16:49 UTCEchelonGraph re-scored
  59. 2026-10-11 14:00 UTCEchelonGraph re-scored
  60. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  61. 2026-10-10 20:07 UTCEchelonGraph re-scored
  62. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  63. 2026-10-09 22:06 UTCEchelonGraph re-scored
  64. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  65. 2026-10-08 21:41 UTCEchelonGraph re-scored
  66. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  67. 2026-10-08 02:34 UTCEchelonGraph re-scored
  68. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  69. 2026-10-06 19:30 UTCEchelonGraph re-scored
  70. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  71. 2026-10-05 21:19 UTCEchelonGraph re-scored
  72. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  73. 2026-10-05 03:34 UTCEchelonGraph re-scored
  74. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  75. 2026-10-03 16:15 UTCEchelonGraph re-scored

Related CVEs(same CWE)

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 (74th 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.

Book a Demo →Browse All CVEs