# CVE-2026-13512: Databend Tenant client_session_manager.rs state_key authorization

> Remote attackers can bypass authorization in Databend's tenant session manager, potentially accessing unauthorized resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-m84g-jvj9-9qg6

## What is CVE-2026-13512?

CVE-2026-13512 is a medium-severity authentication bypass vulnerability in Databend, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-13512 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13512 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13512 is a medium-severity authentication bypass vulnerability in Databend, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13512 exists.

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

## Sources

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

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