Unverified50% confidenceFactExact time
v2.1.289 fixes a vulnerability in enterprise managed machine scenarios where, when nested portions of compound shell commands partially trigger deny/ask rules, those rules might fail to override user-installed mod approvals.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/3/2026
First Seen
Valid until: 1/1/2027
Sources
Related Entities
Related Claims
Unverifiedv2.1.269 fixes a security vulnerability where Edit() deny rules and write-path checks did not cover files written by the Bash tee command.67% similarUnverifiedUnder bypassPermissions mode or shell allow rules, dangerous rm commands targeting the root directory or home directory inside bash -c or sh -c scripts previously ran without prompting; this has been fixed to prompt first (corresponding to issue #96300).65% similarUnverifiedBefore the fix, recursive deletion commands like rm -rf "$(pwd)" whose targets came solely from command substitution output would execute silently without prompting in auto mode and --dangerously-skip-permissions mode; after the fix, the user will be actively asked even if a Bash allow rule exists, unless CLAUDE_CODE_DISABLE_SUBSTITUTION_RM_PROMPT=1 is set.63% similarUnverifiedIf the command does not take effect after configuring the environment variable, it may be due to caching, and restarting the computer can resolve the issue.63% similarUnverifiedCertain destructive shell commands cause damage before the code is even committed, rendering CI scanning powerless against them.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/971048API
curl https://kongchang.com/api/v1/knowledge/claims/971048MCP
get_claim(id=971048)