Cross-tenant session access via tenantless state keys
Published Jun 28, 2026 · Updated Jun 28, 2026
Authorization bypass in Databend 1.2.881 and earlier allows remote authenticated users to access another tenant's HTTP session state. ClientSessionManager::state_key indexes temporary-table state only by user name and a client-supplied session ID, omitting the tenant identity when storing and restoring the state. Exploitation requires matching user names in two tenants and a matching client session ID, enabling one tenant's session to resolve to another tenant's temporary-table state.
Summary
What happened
Authorization bypass in Databend 1.2.881 and earlier allows remote authenticated users to access another tenant's HTTP session state. ClientSessionManager::state_key indexes temporary-table state only by user name and a client-supplied session ID, omitting the tenant identity when storing and restoring the state. Exploitation requires matching user names in two tenants and a matching client session ID, enabling one tenant's session to resolve to another tenant's temporary-table state.
The record
- CVE
- CVE-2026-13512
- Published
- Jun 28, 2026
- Updated
- Jun 28, 2026
- Vendor
- Databend Labs
- Product
- Databend
- Classifications
- CWE-285, CWE-639, T1213.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 28, 2026CVE publishedPublication date reported by the CVE source.
- Jun 28, 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=1.2.881
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
- HTTP session state-key collision reproductionproof of concept · 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