Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-19592: GitSpawn: OpenAI Codex Git fsmonitor Command Execution

Published Sep 1, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.3High · v3.1
EPSS0.16%5th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-19592CWE-78

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in arbitrary code execution under the privileges of the logged-in Codex user. The attacker-controlled code can read, modify, or delete files accessible to that user and access other resources available to the user account.

Mitigation

If you can’t patch tonight, do this now.

Do not open or use untrusted repositories delivered with their Git metadata intact. Before using a received repository, inspect its repository-local Git configuration and remove or unset core.fsmonitor. Administrators and users may also disable core.fsmonitor globally. Vendors invoking Git for background metadata collection can explicitly override core.fsmonitor to false for those calls.

Remediation

Patch, then assume compromise.

Update affected Codex products to fixed releases: Codex CLI 0.131.0 or later; Codex Desktop for macOS 26.519.22136 or later; and Codex Desktop for Windows 26.519.21041 or later. For the Microsoft Store Windows package, update to 26.519.2081.0 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-19592 exploited in the wild?
As of Oct 15, 2026, Mallory has no reports of CVE-2026-19592 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19592?
Yes. As of Oct 15, 2026, Mallory has reports of a public exploit for CVE-2026-19592.
Is there a patch for CVE-2026-19592?
Update affected Codex products to fixed releases: Codex CLI 0.131.0 or later; Codex Desktop for macOS 26.519.22136 or later; and Codex Desktop for Windows 26.519.21041 or later. For the Microsoft Store Windows package, update to 26.519.2081.0 or later.
How severe is CVE-2026-19592?
CVE-2026-19592 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 0.16% (5th percentile) as of Oct 15, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.