Skip to main content
CVE-2025-54558VulnerabilityPublished

CVE-2025-54558: OpenAI Codex CLI · Untrusted Functionality Inclusion

Affects OpenAI Codex CLISource CVE Database V5

0

Not known to be exploited · CVSS 4.1 Medium : upgrade to 0.9.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.0
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade openai/codex to 0.9.0.

Affected software

ProductAffectedFixed in
GitHubopenai/codexpkg:github/openai/codexOther threatsAffected
  • <0.9.0
Fixed in
  • 0.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-54558 effectively, European organizations should: 1) Upgrade OpenAI Codex CLI to version 0.9.0 or later where this vulnerability is addressed. 2) Restrict local access to developer machines and CI/CD environments running Codex CLI to trusted personnel only, employing strict access controls and endpoint security measures. 3) Implement monitoring and alerting for unusual ripgrep executions or CLI behaviors, possibly through enhanced logging or behavioral analytics. 4) Educate developers and users about the risks of interacting with untrusted inputs or commands within the CLI environment to reduce the likelihood of social engineering exploitation. 5) Conduct regular code reviews and static analysis on outputs generated or influenced by Codex CLI to detect anomalies or injected malicious code. 6) Employ sandboxing or containerization for running Codex CLI to isolate its execution environment and limit potential damage from exploitation. 7) Integrate security scanning tools that can detect misuse of command-line tools like ripgrep within development pipelines. These measures go beyond generic patching and address operational and procedural aspects critical to mitigating this vulnerability's risk.

Description

OpenAI Codex CLI before 0.9.0 auto-approves ripgrep (aka rg) execution even with the --pre or --hostname-bin or --search-zip or -z flag.

References

Community reviews

Loading reviews…