ACVE

ACVE advisory

ACVE-2025-0009

Cursor CurXecute can inject an MCP configuration

HIGH · CVSS 8 Unverified advisory — awaiting validation CVSS 8

Status meaning: Unverified advisory — awaiting validation

The configuration

Configuration label
cursor <1.3.0
Affected entries
  • AgentHarness: cursor — SEMVER (introduced 0; fixed 1.3.0)
Matcher
  • all
    • harness.id eq "cursor"
    • harness.version semverRange "<1.3.0"
    • some mcpServers
      • transport exists

Why it is exploitable

What the vulnerability is

Cursor's CurXecute issue concerns an MCP configuration path that can be influenced through repository or other untrusted content. The advisory summary describes injection of an MCP configuration, which can cause the agent to reach a server definition the user did not intend to approve. This record treats Cursor before 1.3.0 as affected.

Which configuration is exposed

The matcher exposes Cursor when harness.id is cursor, harness.version is below 1.3.0, and at least one mcpServers entry has a transport field. The transport-present condition is deliberately broad: it identifies an MCP-capable Cursor configuration, not a particular .cursor/mcp.json file or server. It does not require project scope, a package identity, a URL host, or a specific transport value.

How ACVE detects it

ACVE reads harness.id, harness.version, and the existence of mcpServers[].transport. It cannot reproduce the CurXecute input, inspect the source of the configuration, or determine whether a transport was injected rather than intentionally configured. The finding is therefore a static exposure signal.

Fix

  1. Upgrade Cursor to 1.3.0 or later after confirming the release boundary.
  2. Review MCP configuration sources and accept only server commands, arguments, and URLs that are intentionally managed.

A clean result from this matcher means only that no configured transport was recorded; it does not establish that Cursor cannot receive untrusted project content through another path.

Grounding needed

acve advisory ground must confirm the affected Cursor range and fixed release for CVE-2025-54135.

The matcher cannot establish that a transport was injected rather than intentionally configured.

References

See references for primary sources.

Underlying CVEs / aliases

Detect

npx @pickbitsai/acve audit

For CI, emit SARIF with npx @pickbitsai/acve audit --format sarif --out acve.sarif --apply and upload it with GitHub code scanning.

Fix

Upgrade Cursor to the confirmed fixed release and review MCP configuration sources.

ActionTargetToWhy
upgradeharness:cursor1.3.0Use the fixed release.

Validation

No validation entries recorded.

Grounding

  • OSV: not found; checked-at 2026-09-20T02:43:25Z
  • NVD: not found; checked-at 2026-09-20T02:43:25Z
  • KEV: not listed in KEV; checked-at 2026-09-20T02:43:25Z

References

ADVISORY

REPORT

FIX