# CVE-2025-61260: OpenAI Codex CLI enables code execution through malicious MCP (Model Context Protocol) configuration files

> Attackers can execute arbitrary code by placing malicious configuration files in a repository, affecting developers using the OpenAI Codex CLI.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-xrxf-jgv3-qmrm

## What is CVE-2025-61260?

CVE-2025-61260 is a critical code injection vulnerability in n/a, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in OpenAI Codex CLI v0.23.0 and before that enables code execution through malicious MCP (Model Context Protocol) configuration files. The attack is triggered when a user runs the codex command inside a malicious or compromised repository. Codex automatically loads project-local .env and .codex/config.toml files without requiring user confirmation, allowing attackers to embed arbitrary commands that execute immediately.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-61260?

2 open source packages ship an affected version, including @openai/codex.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@openai/codex` | npm | All versions to 0.23.0 | None |
| `@openai/codex` | npm | All versions to 0.23.0 | None |

## How do I fix CVE-2025-61260?

No fix has been published for CVE-2025-61260 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61260 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61260 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61260 and fix it if it is affected.

What it is: CVE-2025-61260 is a critical code injection vulnerability in n/a, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61260 exists.

Affected packages and fixed versions:
- @openai/codex (npm): affected all versions up to 0.23.0; no fix listed
- @openai/codex (npm): affected all versions up to 0.23.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61260/ (Markdown: https://insights.sbomify.com/CVE-2025-61260/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61260
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61260
- OSV: https://osv.dev/vulnerability/CVE-2025-61260

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61260/
Summaries are generated and may contain mistakes; the official description above is the record.