CVE-2026-76072 Continue CLI through 1.5.47 Incomplete Destructive Command Denylist in Headless and Auto Mode

High 8.3 Published Updated

Incomplete command denylist in Continue CLI allows destructive shell commands via prompt injection in headless or auto mode, risking data loss.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-76072?

CVE-2026-76072 is a high-severity vulnerability in continuedev continue, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The Continue CLI applies an incomplete denylist as its only barrier to destructive shell commands when running unattended. In headless mode and auto mode the default policy in extensions/cli/src/permissions/defaultPolicies.ts grants the Bash tool the allow permission, and permissionChecker.ts hard-blocks a command only when the terminal-security evaluator returns a disabled verdict, so isCriticalCommand in packages/terminal-security/src/evaluateTerminalCommandSecurity.ts is the sole control. Its dangerous-path test matches only /, /*, ~, ~/*, /usr, /etc, /bin and /sbin and their prefixes, so a recursive forced removal of /home, /root, /var, /opt or /srv is not disabled. The command line is parsed with shell-quote, which reduces $HOME to an empty token, so rm -rf $HOME also fails the dangerous-path test while the shell re-expands the variable when the command is spawned. find with -delete is rated high risk rather than disabled, and shred, wipefs, truncate and pkexec are not handled. Because the agent autonomously reads content it does not control, including fetched web pages, repository files and issue text, an indirect prompt injection in that content can cause an unattended run to destroy the invoking user's data.

Weakness: CWE-184

Which versions are affected by CVE-2026-76072?

How do I fix CVE-2026-76072?

No fix has been published for CVE-2026-76072 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-76072 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76072 exists.

Sources

Also known as GHSA-xqr4-4xjv-5j7q.

Is CVE-2026-76072 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free