Codex CLI runs a deletion command from its own security doc
11/11/2026 — 11/11, 04:18·1 sources (all)·1 reports (all)
Key takeaways
- According to GitHub issue #36937, Codex CLI 0.146.0 running on Windows 10 in danger-full-access mode with approval policy set to never passe…
Background & analysis
According to a report published on DEV Community on November 11, 2026, a Codex CLI user asked the agent to audit its own older sessions -- a read-only review task. The audit itself turned destructive, and what made it destructive was Codex's own safety documentation.
The report says that, per GitHub issue #36937, filed against Codex CLI 0.146.0 (model gpt-5.6-sol, Windows 10, via Git Bash, running in danger-full-access mode with approval policy never), Codex's audit step passed the path of an old session's rollout JSONL file into the program position of a Bash login shell. Git Bash then read the file's contents as shell input, and a backtick-wrapped recursive deletion example that existed only to illustrate a "do not execute" warning was instead interpreted as command substitution and actually executed, with the deletion target pointing at the HOME directory.
The available material does not report any follow-up progress on the issue, nor any resolution or conclusion, so the event currently stops at this reported occurrence.
AI-generated from 1 reports · updated 3 days ago
Related AI tools
- Heat index
- 25
- All sources
- 1
- All reports
- 1
- First seen
- 3 days ago
Reports on this story headlines open the original
According to GitHub issue #36937, a Codex CLI 0.146.0 user (model gpt-5.6-sol, Windows 10, danger-full-access mode, approval policy never) asked the agent to audit old sessions, and the audit passed a session JSONL path into the program position of a Bash login-shell call. Git Bash read the file as shell input, so a backtick-quoted recursive-delete example that existed only as documentation of what not to run was executed for real against the HOME directory.
DEV Community · AIAI score 60
Other stories people are talking about
- Heat index 87NewFour Practical Checks for Connecting Codex CLI to Third-Party Models1 sources
- Heat index 71Shared memory for Claude Code and Codex: pull it on demand, don't inject it1 sources
- Heat index 2236Nvidia stock plunges after Jensen Huang resigns, with retail investors buying the dip35 sources
- Heat index 1463RisingGoogle Opens Gemini 4 Hydrogen to All Users as High-Speed Model21 sources
- Heat index 1429SurgeJensen Huang exits as NVIDIA CEO, leadership vacuum lingers16 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion