CVE-2026-19591
HIGHDescription
OpenAI Codex CLI for Windows, macOS, and Linux and Codex Desktop for Windows and macOS misclassified certain PowerShell commands as safe because their command-safety parser interpreted PowerShell's stop-parsing token (--%) differently than PowerShell itself. If a user opens an attacker-prepared repository and Codex follows its instructions, Codex can run a file-writing Git command without requesting user approval. On macOS and Linux, exploitation additionally requires separately installed PowerShell Core (pwsh) to be invoked. If filesystem protections permit the write, the command can modify Codex's configuration. If Codex later loads the modified configuration, it can launch an attacker-controlled MCP server and execute code with the user's privileges, allowing it to read, change, or delete files accessible to that account. The approval bypass does not disable filesystem sandboxing; the default filesystem sandbox on macOS and Linux can prevent writes outside permitted locations.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 23% of all known CVEs.
References
Related Vulnerabilities
Other CWE-150 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-0899 | Critical | 9.8 | 11% | - | Fix |
| CVE-2025-55754 | Critical | 9.6 | 10% | - | Fix |
| CVE-2021-25310 | High | 8.8 | 4.6% | - | - |
| CVE-2020-6932 | Critical | 10.0 | 3.6% | - | - |
| CVE-2024-28085 | Low | 3.3 | 2.2% | - | Fix |
| CVE-2022-30123 | Critical | 10.0 | 1.9% | - | Fix |
Common questions
How do I fix CVE-2026-19591?
No published fix for CVE-2026-19591 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-19591 being actively exploited?
Not that we know of. CVE-2026-19591 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.30% is the estimated probability that it will be exploited in the next 30 days. That is higher than 23% of all scored CVEs.
How severe is CVE-2026-19591?
CVE-2026-19591 has a CVSS v3 base score of 8.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-19591
Markdown
[](https://tridentstack.com/cve/CVE-2026-19591)HTML
<a href="https://tridentstack.com/cve/CVE-2026-19591"><img src="https://tridentstack.com/cve/badge/CVE-2026-19591.svg" alt="CVE-2026-19591"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-02.