HomeIntelligenceBrief
VULNERABILITY BRIEF🟠 High Vulnerability

Remote Code Execution in OpenAI Codex (CVE‑2026‑19590) Enables Arbitrary Code Execution via Malicious Config Files

OpenAI Codex contains CVE‑2026‑19590, a 7.8‑rated flaw that lets attackers execute code after a user opens a malicious page or file. The vulnerability underscores the importance of secure configuration management and auditable remediation for compliance‑focused organizations.

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‑19590) – External Control of System or Configuration Setting

What It Is – A CVE‑2026‑19590 vulnerability in OpenAI Codex allows an attacker who convinces a user to open a malicious page or file to execute arbitrary code on the victim’s machine. The flaw stems from insufficient sanitization of configuration files, leading to external control of system or configuration settings.

Exploitability – The CVSS v3.1 base score is 7.8 (High). Exploitation requires user interaction (visiting a malicious page or opening a crafted file) but no authentication, and a working exploit was demonstrated in the Pwn2Own competition.

Affected Products – OpenAI Codex (the code‑generation model and its runtime environment).

Why It Matters for Trust & Control Assurance

  • Secure Configuration Management – The issue highlights the need for rigorous controls around configuration file handling, a core control objective that underpins many compliance frameworks (e.g., NIST CSF 2.0 ID.AM‑6).
  • Continuous Evidence – Demonstrating that configuration controls are consistently enforced and auditable provides the defensible evidence enterprises demand during security reviews.
  • Vendor Oversight – Organizations that integrate third‑party AI services must verify that vendors apply secure development and patch‑management practices, and retain proof of remediation.

Recommended Actions

  • Apply OpenAI’s patch for CVE‑2026‑19590 immediately.
  • Review and harden your own configuration‑file ingestion pipelines (whitelisting, schema validation, sanitization).
  • Update your control‑mapping inventory to reflect the “Secure Configuration Management” objective and capture remediation evidence.
  • Incorporate the patched state into continuous monitoring dashboards to maintain an audit‑ready posture.

Source: Zero Day Initiative Advisory ZDI‑26‑648

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

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

From the Verisq platform · Trust Operations

Every gap like this maps to a control you can evidence.

The Verisq AI Trust Operations platform maps incidents to your control framework and collects the evidence continuously — so your Trust Center shows proof, not promises, when a buyer or auditor asks.

Explore the Verisq AI Trust Operations platform →