OpenAI Codex CLI up to 0.8.x auto-approves ripgrep inclusion of functionality from untrusted control sphere
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in OpenAI Codex CLI up to 0.8.x and classified as problematic. The affected element is an unknown function of the component auto-approves ripgrep Handler. Performing a manipulation results in inclusion of functionality from untrusted control sphere. This vulnerability is known as CVE-2025-54558. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in OpenAI Codex CLI up to 0.8.x. This affects an unknown part of the component auto-approves ripgrep Handler. The manipulation with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. CWE is classifying the issue as CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-54558 since 07/25/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.9.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 6cf4b96f9dbbef8a94acc1ff703eb118481514d8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.4
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.1
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Inclusion of functionality from untrusted control sphereCWE: CWE-829
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Codex CLI 0.9.0
Patch: 6cf4b96f9dbbef8a94acc1ff703eb118481514d8
Timeline
07/25/2025 Advisory disclosed07/25/2025 CVE reserved
07/25/2025 VulDB entry created
07/25/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-54558 (🔒)
GCVE (CVE): GCVE-0-2025-54558
GCVE (VulDB): GCVE-100-317565
Entry
Created: 07/25/2025 08:43Changes: 07/25/2025 08:43 (66)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.