{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-19591 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-19591 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19591 is a high-severity vulnerability in OpenAI Codex CLI, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-19591 and fix it if it is affected.\n\nWhat it is: CVE-2026-19591 is a high-severity vulnerability in OpenAI Codex CLI, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-19591 in the wild and no public exploit code.\n\nAffected product: OpenAI Codex CLI. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-19591/ (Markdown: https://insights.sbomify.com/CVE-2026-19591/index.md)","id":"CVE-2026-19591","markdown":"https://insights.sbomify.com/CVE-2026-19591/index.md","name":"CVE-2026-19591","record":{"aliases":["GHSA-2frj-4qr5-m2rf"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenAI Codex CLI","requires_auth":"none","summary":"Attackers can bypass approval prompts to modify configuration and execute code via malicious repositories in OpenAI Codex CLI and Desktop.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"OAI","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-150","name":"Improper Neutralization of Escape, Meta, or Control Sequences"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in Codex CLI","id":"CVE-2026-19591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Codex CLI","id":"CVE-2026-19592"},"packages":[],"prev":{"headline":"Code injection in Codex Desktop","id":"CVE-2026-19590"},"products":["Codex CLI","Codex Desktop","Codex Desktop (Microsoft Store package)"],"published":"2026-09-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["OpenAI"]},"summary":"Attackers can bypass approval prompts to modify configuration and execute code via malicious repositories in OpenAI Codex CLI and Desktop.","url":"https://insights.sbomify.com/CVE-2026-19591/"}