HomeIntelligenceBrief
VULNERABILITY BRIEF🟠 High Vulnerability

Remote Code Execution Vulnerability (CVE-2026-19591) in OpenAI Codex Enables Arbitrary Code Execution via Malicious Folder

OpenAI disclosed CVE‑2026‑19591, a remote‑code‑execution flaw in Codex that can be triggered when a user opens a crafted folder. The issue underscores the need for continuous third‑party vulnerability monitoring and auditable patch management to satisfy control‑based compliance frameworks.

LiveThreat™ Intelligence · 📅 September 10, 2026· 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
Actions
4 recommended
📰
Source
zerodayinitiative.com

Remote Code Execution in OpenAI Codex (CVE‑2026‑19591) Allows Arbitrary Code Execution via Malicious Folder

What It Is – A remote‑code‑execution (RCE) flaw (CVE‑2026‑19591) in OpenAI Codex’s handling of git‑command arguments. Insufficient neutralisation of control sequences lets an attacker run arbitrary code when a user opens a crafted folder.

Exploitability – CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploit requires user interaction (opening a malicious folder) but can be triggered remotely without authentication. No public exploit code is known, but the vulnerability was demonstrated by the Compass Security team in a Pwn2Own contest.

Affected Products – OpenAI Codex (the AI‑assisted code generation service).

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous vulnerability monitoring of third‑party AI services that become part of your development pipeline.
  • Highlights the importance of evidence‑based patch management to prove that you are running the vendor‑supplied fix.
  • Affects the control objective of secure software supply chain – one satisfied control maps to multiple frameworks (e.g., NIST CSF, ISO 27001, SOC 2).

Recommended Actions

  • Verify your Codex version and apply OpenAI’s security update immediately.
  • Update your asset inventory to record the patched version as evidence for audit.
  • Incorporate the vulnerability into your continuous control‑mapping process to demonstrate ongoing compliance.
  • Review internal policies for handling user‑initiated file operations that could trigger code execution.

Source: Zero Day Initiative advisory

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-649/

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Answer one control objective. Answer ten frameworks.

The Verisq Common Framework is a spine of 84 control objectives that SOC 2, ISO 27001, NIST CSF, CMMC, HIPAA, PCI DSS, HITRUST, GDPR, ISO 42001 and NIST AI RMF map onto — each graded honestly. Satisfy an objective once and every framework that recognizes it lights up at its real strength.

See how the Verisq Common Framework works →