CVE-2026-19593
When a user opened a workspace with an attacker's local Git settings, affected versions of Codex Desktop could run a program through a Git attribute filter. Codex did not ask the user to trust the workspace or approve the command.
Affected products & versions
Affected products & versions
| Vendor | Product | Platform | Affected versions |
|---|---|---|---|
| OpenAI | Codex Desktop (application) | macOS | 260202.0859–26.513.31313 |
| OpenAI | Codex Desktop (application) | Windows | 26.304.38–26.513.40821 |
| OpenAI | Codex Desktop (Microsoft Store package) | Windows | 26.304.38.0–26.513.4821.0 |
Version ranges are inclusive.
Impact
The Codex command sandbox did not restrict the program. It ran with the signed-in user's permissions. The program could read, change, or delete files and get access to credentials available to the user.
Conditions
Conditions
Git had to be available on PATH. The user had to open a workspace that contained the attacker's local .git/config file and Git attributes. A Git clone does not copy the source repository's local .git/config file.
Known exploitation
Known exploitation
No known abuse in the wild.
Mitigations
Mitigations
- Update Codex Desktop for macOS to application version 26.519.22136 or a subsequent version.
- Update Codex Desktop for Windows to application version 26.519.21041 (Microsoft Store package 26.519.2081.0) or a subsequent version.
- Until you update, do not open workspace folders from untrusted sources if the folders contain
.gitmetadata.
Vulnerability description
When a user opened a workspace, Codex Desktop used Git to read repository metadata and check for file changes. An attacker could use the attr.tree setting and a clean or process filter to make Git run a program during this check. The attack did not require the user to interact with a model.
Problem type
CWE-15(opens in a new window) — External Control of System or Configuration Setting.
Credits
Credits
Satoki Tsuji (@satoki00) / Ikotas Labs, Inc.
References
Author
Publication and revision history
| Date | Change |
|---|---|
| September 1, 2026 | Original publication of the CVE record(opens in a new window). |
| October 30, 2026 | Publication on openai.com. |