# CVE-2026-49989: CrateDB's Blob HTTP handler bypasses authorization

> Authenticated users can read, delete, or create blobs in any table via the HTTP API, bypassing SQL privilege checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-2xv8-gjwh-fv8p

## What is CVE-2026-49989?

CVE-2026-49989 is a high-severity missing authorization vulnerability in crate, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CrateDB is a distributed SQL database. Prior to versions 6.2.8 and 6.3.2, any authenticated user can read or delete any blob whose SHA-1 digest they know, and can plant new blobs unconditionally, in any blob table, regardless of `GRANT`s. CrateDB has two ways to access blob storage: SQL (`SELECT ... FROM blob.<table>` and friends) and the blob HTTP API (`GET|PUT|DELETE /_blobs/{table}/{digest}`). The SQL path goes through `AccessControl`, which is what enforces privilege grants; that's why `SELECT digest FROM blob.secret_blobs` fails for a user who has no grants on the table. The HTTP path authenticates the request but never asks `AccessControl` whether the authenticated user is allowed to touch the table. So a user with no grants gets `MissingPrivilegeException` from SQL and `200 OK` plus the blob bytes from `GET /_blobs/secret_blobs/<digest>`. Deployments that don't use `BLOB TABLE` are unaffected. Authentication itself still works; the bug is strictly that being authenticated as anyone is treated as sufficient for any blob op. Versions 6.2.8 and 6.3.2 fix the issue.

Weakness: CWE-863 (Incorrect Authorization)

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

4 open source packages ship an affected version, including io.crate:crate.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.crate:crate` | Maven | All versions | 6.2.8 |
| `io.crate:crate` | Maven | All versions | 6.2.8 |
| `io.crate:crate` | Maven | From 6.3.0 | 6.3.2 |
| `io.crate:crate` | Maven | From 6.3.0 | 6.3.2 |

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

Upgrade io.crate:crate to a fixed version for your release line: 6.2.8 or 6.3.2.

## Is CVE-2026-49989 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49989 is a high-severity missing authorization vulnerability in crate, published on 14 Aug 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-49989 exists.

Affected packages and fixed versions:
- io.crate:crate (Maven): affected all versions; fixed in 6.2.8
- io.crate:crate (Maven): affected all versions; fixed in 6.2.8
- io.crate:crate (Maven): affected from 6.3.0; fixed in 6.3.2
- io.crate:crate (Maven): affected from 6.3.0; fixed in 6.3.2

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

## Sources

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

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