Skip to content

← Actionable
Critical, CVSS 9.8amended

OpenAI Codex CLI enables code execution through malicious MCP (Model Context Protocol) configuration files

CVE-2025-61260GHSA-xrxf-jgv3-qmrm

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm @openai/codex

    Affected
    <= 0.23.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-61260: 6.58% estimated exploitation activity in the next 30 days; percentile 93.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xrxf-jgv3-qmrm

  2. Revision 2 · amended ·

    Amended from osv record GHSA-xrxf-jgv3-qmrm

  3. Revision 1 · created ·

    Published from ghsa record GHSA-xrxf-jgv3-qmrm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-61260

Advisory: OpenAI Codex CLI enables code execution through malicious MCP (Model Context Protocol) configuration files
IDs: CVE-2025-61260, GHSA-xrxf-jgv3-qmrm
Record: https://patchnext.com/advisories/cve-2025-61260 (revision 3, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @openai/codex: affected <= 0.23.0

## Suggested inspection (read-only)
- `npm ls @openai/codex --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @openai/codex.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xrxf-jgv3-qmrm (GitHub-reviewed advisory GHSA-xrxf-jgv3-qmrm lists affected ranges: npm @openai/codex >=0 <=0.23.0)
- Verified: https://osv.dev/vulnerability/GHSA-xrxf-jgv3-qmrm (OSV record GHSA-xrxf-jgv3-qmrm lists affected ranges: npm @openai/codex >=0 <=0.23.0)

Commands are suggestions: review each one before running it.

Loading voting…