CVE-2026-30310
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSixth's automatic terminal command execution feature has a prompt injection vulnerability that allows attackers to bypass the user approval requirement. By wrapping malicious commands in a specific template, attackers can trick the AI model into misclassifying dangerous commands as 'safe', causing them to be auto-executed without user consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Sixth installation and versionRun 'sixth --version' or locate the Sixth binary, then compare the version against vendor release notes or security advisories for CVE-2026-30310Affected if The installed version matches unpatched releases containing the vulnerability
-
Verify automatic command execution feature is enabledExamine Sixth's configuration files (typically in ~/.sixth/config, ~/.config/sixth/config, or /etc/sixth/) for settings like 'auto_execute', 'ai_classify', 'command_approval', or similar AI-related optionsAffected if The automatic terminal command execution feature with AI-based safety classification is turned on (not disabled or set to require approval for all commands)
-
Review command execution logs for unapproved commandsInspect Sixth's logs (commonly in ~/.sixth/logs/, ~/.local/share/sixth/logs/, or via journalctl -u sixth) and look for commands that executed without the typical approval prompt, especially those with unusual formatting or templatesAffected if Logs show commands that bypassed the approval requirement, or contain patterns consistent with injection templates (specific keywords, brackets, or prefixes designed to manipulate AI classification)
-
Audit system for unexpected command executionCross-reference Sixth's command history with known legitimate activity by reviewing shell history, process logs, or audit logs (auditd, syslog) for commands that originated from Sixth but were not explicitly approved by the userAffected if Commands appear in system logs that were executed through Sixth but the user did not consciously approve them, indicating possible exploitation
A user is affected if Sixth with AI-powered automatic command classification is installed and enabled, the version is unpatched, and evidence exists of commands executing without user approval or of injection template patterns in logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable automatic command execution and require explicit user approval for all commands; implement input validation to detect and block prompt injection patterns before they reach the model.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30310 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data