Security readout for executives and security teams
Plain-English summary
CVE-2025-61260 affects OpenAI Codex CLI v0.23.0 and earlier. A malicious repository can include local configuration files that Codex loads automatically, causing commands to run when a user starts Codex in that repository. This creates a serious risk to developer workstations and any automation that runs Codex on untrusted code.
Executive priority
Treat as urgent for engineering environments using Codex CLI. Prioritize inventory and containment because compromise could expose source code, credentials, and developer machines. If Codex is not deployed, business exposure is likely low.
Technical view
The reported issue is CWE-94 code execution through malicious MCP configuration in project-local .env and .codex/config.toml files. Codex CLI automatically loads these files without user confirmation. The CVSS 3.1 score is 9.8, but the described trigger requires Codex to be run inside a malicious or compromised repository.
Likely exposure
Organizations using OpenAI Codex CLI v0.23.0 or earlier are exposed, especially developers, build systems, or review workflows that open third-party, forked, or compromised repositories and run the codex command there.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The attack scenario is repository-based: an attacker places malicious local configuration files, and execution occurs when Codex is run in that repository.
Researcher notes
The source bundle identifies the product and version range in the description, but affected CPE metadata is not populated. Patch details are not provided in the bundle. Analysis should stay tied to CVE records and the Check Point research until vendor remediation details are confirmed.
Mitigation direction
- Identify systems using OpenAI Codex CLI v0.23.0 or earlier.
- Check OpenAI or project guidance for a fixed version or official workaround.
- Avoid running Codex in untrusted or newly cloned repositories until remediated.
- Review repositories for unexpected .env and .codex/config.toml files.
- Restrict developer tooling permissions where practical.
Validation and detection
- Inventory Codex CLI versions across developer endpoints and automation.
- Confirm whether Codex runs against third-party, forked, or unreviewed repositories.
- Check for project-local .env and .codex/config.toml files in sensitive repositories.
- Verify remediation against official vendor or project release guidance.
- Monitor endpoint and developer telemetry for unexpected process execution from Codex sessions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-61260 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://research.checkpoint.com/2025/openai-codex-cli-command-injection-vulnerability/CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.