Live › vulnerability › CVE-2026-77474
Go to dashboarddestructive_command_guard (dcg) is a safety tool that blocks destructive shell commands before AI coding agents run them. Before 0.6.6, nested or unclosed $( and $(( substitutions trigger exponential rescanning, so the PreToolUse hook hangs and fails open, letting the destructive command run.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running destructive_command_guard before 0.6.6 as a PreToolUse hook for AI coding agents. The flaw is triggered by a destructive command followed by nested or unclosed $( or $(( sequences, so exposure depends on the agent feeding such commands to the hook. Teams not using dcg, or on 0.6.6 or later, can skip it.
No product ranges from the sources yet.
dcg --version and confirm it reports a version earlier than 0.6.6.0.6.6 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
destructive_command_guard (dcg) is a command-line safety tool that blocks destructive shell commands before AI coding agents run them. Prior to 0.6.6, nested or unclosed substitutions are recursively rescanned after an inner scan returns unterminated, producing exponential-time work. The affected scanners are reached through split_command_segments in src/packs/mod.rs. a destructive command followed by nested or unclosed $( or $(( sequences. nested or unclosed $( and $(( sequences cause repeated rescanning of the remaining command suffix. a hung PreToolUse hook fails open, allowing the destructive command to proceed. This issue is fixed in version 0.6.6.
This page as .md · .json · in your agent: get_signal("CVE-2026-77474")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.