Loading vulnerability…
OpenAI Codex CLI and Codex Desktop automatically collected Git repository metadata while honoring the repository-local Git core.fsmonitor setting. An attacker can prepare and distribute a repository whose retained local Git configuration specifies an attacker-controlled filesystem-monitor helper. When Codex performs Git metadata operations, Git may execute that helper. Execution occurs outside Codex's command sandbox and without a user-approval prompt.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Git-configuration command-execution flaw affecting Codex. A repository-preserved .git/config can cause Codex background Git operations to execute attacker-controlled commands outside the Codex sandbox and approval workflow.
A code-execution vulnerability in OpenAI Codex CLI and Codex Desktop caused by honoring an attacker-controlled Git repository-local core.fsmonitor helper during repository metadata collection. A specially delivered or copied repository retaining its .git/config can execute attacker code with the user's privileges, outside the Codex command sandbox.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.