CrateDB's Blob HTTP handler bypasses authorization (CVE-2026-49989) | HOL Guard CVE

Low · CVSS 7.1CVE-2026-49989GHSA-2XV8-GJWH-FV8P

CrateDB's Blob HTTP handler bypasses authorization

Answer in brief

CVE-2026-49989 records a Low severity (CVSS 7.1) vulnerability in CrateDB's Blob HTTP handler bypasses authorization. The current sources do not mark it as known exploited. The current feed maps crate/crate (generic), io.crate:crate (maven), io.crate:crate (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 14, 2026Updated Aug 14, 2026Source checked Sep 17, 2026First seen by HOL Jul 1, 2026Material review Aug 14, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps crate/crate (generic), io.crate:crate (maven), io.crate:crate (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
crate/crategeneric	< 6.2.8 \|\| >= 6.3.0, < 6.3.2	Not reported
io.crate:cratemaven	<6.2.8	6.2.8
io.crate:cratemaven	>=6.3.0,<6.3.2	6.3.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for crate/crate, io.crate:crate, io.crate:crate.
Review the reported fix. Update io.crate:crate to 6.2.8; io.crate:crate to 6.3.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 1, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.