dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-61613

HIGH · 7.7 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cursor is a code editor built for programming with AI. Prior to the Cloud Agent fix on 03/31/2026, browser-enabled Cursor Cloud Agent sessions allowed attacker-controlled web content to connect from inside the agent container to an unauthenticated local agent endpoint, enabling code execution within the affected Cloud Agent sandbox or session and access to files, repository contents, environment variables, credentials, and GitHub App access tokens available to that session. This issue was fixed on 03/31/2026 by requiring authentication for the relevant agent endpoint.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cursor Cloud Agent had an unauthenticated local endpoint that could be reached from attacker-controlled web content within the agent container. This allowed code execution inside the Cloud Agent sandbox with access to files, repository contents, environment variables, credentials, and GitHub App tokens. The fix required authentication for the affected endpoint.

MitigationEnsure Cursor is updated to the version released on or after 03/31/2026 which includes the authentication requirement. Audit logs for any unauthorized access and rotate potentially exposed credentials or tokens.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Cursor installation
    Search for Cursor executables in common installation paths: Windows: %LOCALAPPDATA%\Programs\cursor, macOS: /Applications/Cursor.app, Linux: ~/.cursor or /opt/cursor. Also check via command line: 'where cursor' (Windows) or 'which cursor' (macOS/Linux).
    Affected if Cursor IDE is found installed on the system.
  2. Retrieve installed Cursor version
    Run the Cursor executable with version flag: 'cursor --version' or 'cursor -v' from command line. On macOS, right-click Cursor.app > Get Info to view version. On Windows, check Programs and Features or the executable properties.
    Affected if A version number is returned by the version command or found in application details.
  3. Identify if Cloud Agent feature is in use
    Look for running Cursor processes related to cloud agent: check task manager or running processes for 'cursor-cloud-agent', 'cursor-agent', or similar. Also inspect Cursor settings (settings.json) for 'cloudAgent', 'remoteAgent', or 'aiAgent' configuration entries that indicate the feature is enabled.
    Affected if Cloud Agent feature is enabled in settings or a related process is running.
  4. Compare version to fixed release
    Compare the retrieved version number against versions released on or after 03/31/2026. Since exact version numbers are not provided, treat any version released before late March 2026 as potentially vulnerable if Cloud Agent is enabled. Check Cursor's official release notes or changelog for version dates if available.
    Affected if The installed version was released before 03/31/2026 and Cloud Agent feature is enabled.

The environment is affected if Cursor IDE with Cloud Agent enabled is installed at a version released before 03/31/2026, as the vulnerability allows unauthenticated code execution from attacker-controlled web content within the agent container.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure Cursor is updated to the version released on or after 03/31/2026 which includes the authentication requirement. Audit logs for any unauthorized access and rotate potentially exposed credentials or tokens.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61613 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data