CVE-2026-19590
When a user opened a repository that kept an attacker's local Git settings, affected versions of Codex Desktop could run the attacker's Git hook. The Codex command sandbox did not restrict the hook, and Codex did not ask for approval.
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 hook ran with the user's permissions. It could read, change, or delete the user's files and use other resources available to the user's account.
Conditions
Conditions
Git had to be installed. The user had to open or use a copy of a repository whose local .git/config set core.hooksPath to a directory the attacker controlled. 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 untrusted repository archives or copies that include the source repository's
.git/configfile.
Vulnerability description
A Git hook is a program that Git runs during certain operations. Affected versions of Codex Desktop used the repository's core.hooksPath setting during automatic Git operations. This setting could direct Git to a hook in the attacker's directory.
Problem type
CWE-427(opens in a new window) — Uncontrolled Search Path Element.
Credits
Credits
Sina Kheirkhah (@SinSinology) of Summoning Team (@SummoningTeam).
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. |