CVE-2026-61613

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.7Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

July 21, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Cloud Agent Browser Sandbox Escape · Advisory · cursor/cursor · GitHub

https://github.com/cursor/cursor/security/advisories/GHSA-whx2-4gvm-m3r3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 128 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-13 13:22 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-12 15:50 UTCEG score recompute
  5. 2026-10-11 19:34 UTCEG score recompute
  6. 2026-10-11 16:49 UTCEG score recompute
  7. 2026-10-11 14:11 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-01 12:41 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-09-28 08:46 UTCEG score recompute
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-09-24 08:53 UTCEG score recompute
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 74 more
  1. 2026-09-23 03:19 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-09-18 04:46 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-09-13 23:13 UTCEG score recompute
  8. 2026-09-13 07:14 UTCEG score recompute
  9. 2026-09-11 21:46 UTCEG score recompute
  10. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-09-08 00:56 UTCEG score recompute
  14. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-09-05 20:51 UTCEG score recompute
  17. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  19. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-08-31 03:58 UTCEG score recompute
  22. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-08-30 03:53 UTCEG score recompute
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  26. 2026-08-28 01:52 UTCEG score recompute
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  28. 2026-08-26 23:32 UTCEG score recompute
  29. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  30. 2026-08-25 21:07 UTCEG score recompute
  31. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  32. 2026-08-24 20:42 UTCEG score recompute
  33. 2026-08-23 09:51 UTCEG score recompute
  34. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-08-22 10:50 UTCEG score recompute
  36. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-08-20 23:46 UTCEG score recompute
  38. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  39. 2026-08-20 00:17 UTCEG score recompute
  40. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  41. 2026-08-18 21:54 UTCEG score recompute
  42. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-08-17 21:23 UTCEG score recompute
  44. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-08-16 18:33 UTCEG score recompute
  46. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-08-16 07:02 UTCEG score recompute
  48. 2026-08-15 08:01 UTCEG score recompute
  49. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  50. 2026-08-14 08:56 UTCEG score recompute
  51. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  52. 2026-08-12 22:21 UTCEG score recompute
  53. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  54. 2026-08-11 23:20 UTCEG score recompute
  55. 2026-08-11 00:18 UTCEG score recompute
  56. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  57. 2026-08-09 13:47 UTCEG score recompute
  58. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  59. 2026-08-09 02:17 UTCEG score recompute
  60. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  61. 2026-08-08 03:16 UTCEG score recompute
  62. 2026-08-06 16:44 UTCEG score recompute
  63. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  64. 2026-08-06 05:14 UTCEG score recompute
  65. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  66. 2026-08-04 17:17 UTCEG score recompute
  67. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  68. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  69. 2026-08-02 07:21 UTCEG score recompute
  70. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  71. 2026-08-01 08:19 UTCEG score recompute
  72. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  73. 2026-07-30 21:41 UTCEG score recompute
  74. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61613?
CVE-2026-61613 is a high-severity vulnerability; its CVE record was published on July 15, 2026. 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…
When was the CVE record for CVE-2026-61613 published?
The CVE record for CVE-2026-61613 was published on July 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-61613 actively exploited?
CVE-2026-61613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61613?
CVE-2026-61613 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61613?
No fix for CVE-2026-61613 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61613

Explore →

Is Your Infrastructure Affected by CVE-2026-61613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs