OpenAI Codex Desktop for Windows and macOS could execute attacker-controlled Git hooks because automated Git operations trusted the repository's local core.hooksPath setting. If a user opens an attacker-prepared repository whose preserved .git/config points core.hooksPath to an attacker-controlled directory, Codex can run a malicious hook while processing the repository. The hook executes outside Codex's command sandbox, without user approval, and with the user's privileges, allowing it to read, change, or delete the user's files and access other resources available to the user's account. An ordinary Git clone does not preserve the attacker-controlled repository-local configuration required for exploitation.
CVE-2026-19590
Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
September 1, 2026
Last Modified
September 3, 2026
Advisory Details (1)
Auto-updated Sep 3, 2026Ignore configured hooks in git helpers
Fix merged in openai/codex PR #22843 on 2026-05-15 — awaiting tagged release
https://github.com/openai/codex/pull/22843Vendor Advisories for CVE-2026-19590(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 72× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 07:14 UTCGHSA enrichment
- 2026-09-19 19:54 UTCEG score recompute
- 2026-09-19 19:53 UTCGHSA enrichment
- 2026-09-19 08:44 UTCGHSA enrichment
- 2026-09-18 21:25 UTCEG score recompute
- 2026-09-18 21:25 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 09:11 UTCGHSA enrichment
- 2026-09-17 22:02 UTCEG score recompute
- 2026-09-17 22:02 UTCGHSA enrichment
- 2026-09-17 10:53 UTCGHSA enrichment
- 2026-09-16 23:44 UTCEG score recompute
- 2026-09-16 23:44 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 12:34 UTCEG score recompute
- 2026-09-16 12:34 UTCGHSA enrichment
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-16 01:25 UTCGHSA enrichment
- 2026-09-15 14:16 UTCEG score recompute
- 2026-09-15 14:16 UTCGHSA enrichment
- 2026-09-15 03:06 UTCGHSA enrichment
- 2026-09-14 15:57 UTCGHSA enrichment
- 2026-09-14 04:48 UTCGHSA enrichment
- 2026-09-13 17:39 UTCEG score recompute
- 2026-09-13 17:39 UTCGHSA enrichment
Show 47 moreShow fewer
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 06:30 UTCGHSA enrichment
- 2026-09-12 19:21 UTCEG score recompute
- 2026-09-12 19:21 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 08:12 UTCGHSA enrichment
- 2026-09-11 21:02 UTCEG score recompute
- 2026-09-11 21:02 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:53 UTCEG score recompute
- 2026-09-11 09:53 UTCGHSA enrichment
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 22:44 UTCGHSA enrichment
- 2026-09-10 11:35 UTCEG score recompute
- 2026-09-10 11:35 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-09 23:36 UTCGHSA enrichment
- 2026-09-09 10:32 UTCGHSA enrichment
- 2026-09-08 23:22 UTCEG score recompute
- 2026-09-08 23:22 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 07:18 UTCGHSA enrichment
- 2026-09-07 20:09 UTCGHSA enrichment
- 2026-09-07 08:58 UTCGHSA enrichment
- 2026-09-06 21:41 UTCEG score recompute
- 2026-09-06 21:41 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 10:31 UTCGHSA enrichment
- 2026-09-05 23:23 UTCEG score recompute
- 2026-09-05 23:23 UTCGHSA enrichment
- 2026-09-05 12:13 UTCGHSA enrichment
- 2026-09-05 01:02 UTCEG score recompute
- 2026-09-05 01:02 UTCGHSA enrichment
- 2026-09-04 13:52 UTCEG score recompute
- 2026-09-04 13:52 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-04 02:42 UTCEG score recompute
- 2026-09-04 02:41 UTCGHSA enrichment
- 2026-09-03 15:31 UTCGHSA enrichment
- 2026-09-03 14:47 UTCEG score recompute▲ 7.30
- 2026-09-03 14:46 UTCGHSA enrichment
- 2026-09-03 14:43 UTCMITRE cvelistV5CVSS v3 → 7.3 · severity → HIGH
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 21:07 UTCGHSA enrichment
- 2026-09-01 18:22 UTCNVD update
- 2026-09-01 17:22 UTCEG score recompute
- 2026-09-01 17:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-19590?
When was CVE-2026-19590 disclosed?
Is CVE-2026-19590 actively exploited?
What is the CVSS score of CVE-2026-19590?
How do I remediate CVE-2026-19590?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19590
Is Your Infrastructure Affected by CVE-2026-19590?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.