In its design for automatic terminal command execution, Sixth offers two options: Execute safe commands and Execute all commands. The description for the former states that commands determined by the model to be safe will be automatically executed, whereas if the model judges a command to be potentially destructive, it still requires user approval. However, this design is highly susceptible to prompt injection attacks. An attacker can employ a generic template to wrap any malicious command and mislead the model into misclassifying it as a 'safe' command, thereby bypassing the user approval requirement and resulting in arbitrary command execution.
CVE-2026-30310
CRITICALPre-NVD 9.89.8—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-31. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
March 31, 2026
Last Modified
July 25, 2026
Advisory Details (2)
Auto-updated Jul 25, 2026No patch confirmed yet.
generic
Sixth Remote Code Execution Vulnerability · Issue #12 · Secsys-FDU/LLM-Tool-Calling-CVEs · GitHub
https://github.com/Secsys-FDU/LLM-Tool-Calling-CVEs/issues/12Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 10:12 UTCEG score recompute
- 2026-07-25 10:12 UTCGHSA enrichment
- 2026-07-25 10:12 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-77
- CVE-2015-7541EG 10.0CRITICAL
- CVE-2015-1815EG 10.0EPSS p97HIGH
- CVE-2014-1905EG 10.0EPSS p95HIGH
- CVE-2013-2810EG 10.0EPSS p93HIGH
- CVE-2014-5470EG 9.8EPSS p95CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS p94CRITICAL
- CVE-2014-4982EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-30310?
CVE-2026-30310 is a critical vulnerability published on March 31, 2026. In its design for automatic terminal command execution, Sixth offers two options: Execute safe commands and Execute all commands. The description for the former states that commands determined by the model to be safe will be automatically executed, whereas if the model judges a command to be…
When was CVE-2026-30310 disclosed?
CVE-2026-30310 was first published in the National Vulnerability Database on March 31, 2026, with the most recent update on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-30310 actively exploited?
CVE-2026-30310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.4% of all scored CVEs.
What is the CVSS score of CVE-2026-30310?
CVE-2026-30310 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-30310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-30310, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-30310
Is Your Infrastructure Affected by CVE-2026-30310?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.