CVE-2026-76072 continuedev CVE debrief

Who should care

Users of the Continue CLI, especially those using headless or auto modes, should assess their exposure and verify the version they are using. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and update the denylist to include all risky commands and paths, and implement additional security measures to prevent indirect prompt injections. Affected users must also review compensating and  

Why it matters

The Continue CLI is vulnerable to destructive shell commands when running in unattended mode due to an incomplete denylist. Users of the Continue CLI, especially those using headless or auto modes, should assess their exposure and verify the version they are using.

• Potential data destruction if an indirect prompt injection occurs
• Need to verify the version of Continue CLI being used
• Need to review and update the denylist to include all risky commands and paths

Technical summary

The Continue CLI applies an incomplete denylist as its only barrier to destructive shell commands when running unattended. The denylist only blocks certain paths and does not handle all risky commands, such as find with -delete, shred, wipefs, truncate, and pkexec. This incomplete denylist allows for potential data destruction if an indirect prompt injection occurs. The CLI's denylist is defined in extensions/cli/src/permissions/defaultPolicies.ts and is enforced in permissionChecker.ts. The isCriticalCommand function in packages/terminal-security/src/evaluateTerminalCommandSecurity.ts is the sole control for blocking commands.

Defensive priority

High

Recommended defensive actions

• Assess exposure by verifying the version of Continue CLI being used
• Review and update the denylist to include all risky commands and paths
• Implement additional security measures to prevent indirect prompt injections
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source references indicate that the Continue CLI has an incomplete denylist for destructive shell commands in headless and auto modes. The denylist only blocks certain paths and does not handle all risky commands.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.