Cross-tenant queue manipulation via missing ownership checks
Published Jul 24, 2026 · Updated Jul 24, 2026
Broken access control in Kortix Suna before 0.9.102 allows remote authenticated users to manipulate other tenants' message queues. The /v1/queue handlers use a caller-supplied session ID to read, enqueue, or clear filesystem-backed queues without consulting the authenticated user ID or session ownership. Any registered account can expose or delete pending prompts and inject instructions that the drainer forwards to another tenant's running agent under that tenant's credentials and permissions.
Summary
What happened
Broken access control in Kortix Suna before 0.9.102 allows remote authenticated users to manipulate other tenants' message queues. The /v1/queue handlers use a caller-supplied session ID to read, enqueue, or clear filesystem-backed queues without consulting the authenticated user ID or session ownership. Any registered account can expose or delete pending prompts and inject instructions that the drainer forwards to another tenant's running agent under that tenant's credentials and permissions.
The record
- CVE
- CVE-2026-66027
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- Kortix
- Product
- Suna
- Classifications
- CWE-862, T1190, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.9.102
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Cross-Tenant IDOR and Global Queue Drain proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo