External risk intelligence

Sixth Prompt Injection Leads to Arbitrary Command Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-30310

This vulnerability exists within an LLM-based terminal command execution tool. Such tools are typically utilized by individual developers or in internal development environments to automate local tasks. They are not designed as internet-facing services or gateways, making public internet exposure and reachability in common deployments very unlikely.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This CVE describes a vulnerability in a tool that automatically executes terminal commands based on AI analysis. The tool's design to differentiate between safe and potentially destructive commands can be tricked by attackers through prompt injection, allowing them to execute arbitrary commands without user approval.

  • Malicious commands can bypass safety checks.
  • Critical flaw in AI command execution design.
  • Confirm relevance and exposure of this tool.

Attack Path

How an attacker could exploit the issue

An attacker can trick an LLM-powered tool into running any command on a system by disguising a malicious command as a safe one. This bypasses the need for user approval, allowing the attacker to execute arbitrary commands with the tool's permissions. The vulnerability exploits the tool's design for automatically executing commands, which can be misled by carefully crafted input.

  • No prior access needed.
  • Malicious command wrapped as safe.
  • Arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, this vulnerability could allow an attacker to execute arbitrary commands on a system by tricking the tool into misclassifying a malicious command as safe. This bypasses the need for user approval, potentially leading to unauthorized system access or modification.

  • System commands and execution.
  • Malicious commands disguised as safe.
  • Arbitrary command execution occurs.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Sixth's automatic terminal command execution impacts users susceptible to prompt injection attacks. Technical leaders and security teams must first identify instances of Sixth, determine their reachability and business criticality, and locate the accountable owner to plan risk-based remediation.

  • Identify and assess Sixth deployments.
  • Verify reachability and criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Sixth tool and how is it used?

Sixth is an AI-powered software tool designed to automate terminal command execution. It uses a model to analyze commands, attempting to distinguish between safe actions that can run automatically and potentially destructive ones that require manual user approval to prevent system damage.

What does CWE-77 mean for CVE-2026-30310?

CWE-77 is a weakness class known as Improper Neutralization of Special Elements used in a Command. In this CVE, it describes how the AI tool fails to properly sanitize or validate input, allowing attackers to inject malicious code that the system mistakenly interprets as safe, ultimately triggering unauthorized command execution.

How does an attacker trigger this command injection?

An attacker triggers this vulnerability by providing a crafted prompt that masks a malicious command within a template designed to deceive the AI model. The bug is not triggered by standard, benign interactions but specifically relies on this deceptive input structure to bypass the tool's built-in safety classifier and force execution.

Is my instance of Sixth at risk according to Halo Surface Signal?

Halo Surface Signal notes that this vulnerability exists in a tool intended for individual development or internal automation tasks, not as an internet-facing gateway. Consequently, it considers widespread public internet exposure to be very unlikely, though users should still verify if their specific deployment is accessible from outside their internal network.

When should I prioritize a response to this vulnerability?

Prioritize your response by first identifying every system in your environment where Sixth is installed. Once you have a clear inventory, determine if those systems are exposed to untrusted networks or handle sensitive data. Work with the designated system owners to confirm their usage and plan risk-appropriate updates or mitigation strategies.

References