# CVE-2026-61613: Cursor: Cloud Agent Browser Sandbox Escape

> Attackers can execute code and access sensitive data in Cursor Cloud Agent sessions by exploiting an unauthenticated local endpoint.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 21 Jul 2026

## What is CVE-2026-61613?

CVE-2026-61613 is a high-severity missing authorization vulnerability in cursor, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-61613?


## How do I fix CVE-2026-61613?

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

## Is CVE-2026-61613 being exploited?

There is no known exploitation of CVE-2026-61613 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61613 and fix it if it is affected.

What it is: CVE-2026-61613 is a high-severity missing authorization vulnerability in cursor, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-61613 in the wild and no public exploit code.

Affected product: cursor. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-61613/ (Markdown: https://insights.sbomify.com/CVE-2026-61613/index.md)
```

## Sources

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

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