Quick answers
- Is CVE-2026-19593 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19593 being exploited in the wild.
- How severe is CVE-2026-19593?
- Critical severity, with a CVSS score of 9.8, published 1 September 2026.
- Which products and versions are affected?
- OpenAI Codex Desktop all versions prior to patch.
- Is there a fix for CVE-2026-19593?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-19593 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19593?
- Check whether you run OpenAI Codex Desktop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a local code execution flaw in OpenAI Codex Desktop's workspace initialization. When a workspace is opened, Codex automatically runs Git commands to inspect repository metadata and working-tree status. An attacker can place a crafted .git/config file (via a tar/zip archive or shared repository export) that defines malicious clean or process filters using the attr.tree setting. Git will execute the attacker-controlled command on next inspection, running outside Codex's sandbox and without workspace-trust prompts or command approval. Exploitation requires Git to be installed on the user's PATH and the repository to retain its local .git/config (standard Git clones strip this, but archives or explicit pulls preserve it). The attacker gains file system and credential access as the signed-in user.
Affected products
- OpenAI Codex Desktop all versions prior to patch
Timeline
- 2026-09-01: disclosed