Suna before 0.9.102 contains a broken access control vulnerability in the message queue API that allows authenticated attackers to access and manipulate queue resources belonging to other users by exploiting missing ownership and account isolation checks. Attackers can read pending prompt queues of all users, read or delete individual sessions, and inject arbitrary prompts into another user's session queue, causing the background drainer to forward malicious messages to the victim's running AI agent with the victim's credentials and permissions.
CVE-2026-66027
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 8.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(high)
- EG Risk
- 53(Track*)EG Risk 53/100SSVC: Track*
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 computedSeverity83% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 30, 2026
Advisory Details (5)
Auto-updated Jul 24, 2026Suna < 0.9.102 Broken Access Control via Message Queue API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/suna-broken-access-control-via-message-queue-apiv0.9.102 — slack bind-thread + pending main
Patch available: kortix-ai/suna v0.9.102
https://github.com/kortix-ai/suna/releases/tag/v0.9.102fix(security): full security pass — 30 verified findings (2 crit, 14 high, 8 med, 6 low)
Fix merged in kortix-ai/suna PR #4373 on 2026-07-10 — awaiting tagged release
https://github.com/kortix-ai/suna/pull/4373commit 7536a7d47fc9 (kortix-ai/suna)
Fix landed in kortix-ai/suna commit 7536a7d47fc9 — awaiting tagged release
https://github.com/kortix-ai/suna/commit/7536a7d47fc93abcb66e677fcc993b390c81296aVendor Advisories for CVE-2026-66027(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 42× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-03 14:05 UTCEG score recompute
- 2026-08-03 14:05 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 02:27 UTCGHSA enrichment
- 2026-08-02 14:50 UTCGHSA enrichment
- 2026-08-02 03:12 UTCEG score recompute
- 2026-08-02 03:12 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 15:34 UTCEG score recompute
- 2026-08-01 15:34 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-08-01 03:56 UTCGHSA enrichment
- 2026-07-31 16:14 UTCGHSA enrichment
- 2026-07-31 04:36 UTCGHSA enrichment
- 2026-07-30 16:58 UTCEG score recompute
- 2026-07-30 16:58 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 13:00 UTCEG score recompute
- 2026-07-30 12:59 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:21 UTCGHSA enrichment
- 2026-07-29 13:39 UTCGHSA enrichment
- 2026-07-29 02:01 UTCEG score recompute
- 2026-07-29 02:01 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
Show 17 moreShow fewer
- 2026-07-28 14:21 UTCGHSA enrichment
- 2026-07-28 02:41 UTCGHSA enrichment
- 2026-07-27 15:04 UTCEG score recompute
- 2026-07-27 15:04 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 02:14 UTCEG score recompute
- 2026-07-27 02:14 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:36 UTCEG score recompute
- 2026-07-26 14:36 UTCGHSA enrichment
- 2026-07-26 02:59 UTCEG score recompute
- 2026-07-26 02:58 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 15:42 UTCEG score recompute
- 2026-07-24 15:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-66027?
When was CVE-2026-66027 disclosed?
Is CVE-2026-66027 actively exploited?
What is the CVSS score of CVE-2026-66027?
How do I remediate CVE-2026-66027?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66027
Is Your Infrastructure Affected by CVE-2026-66027?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.