Skip to content

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

HighCVSS 7.1 EPSS 0.47%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial

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 GRANTs. 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.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
io.crate/crate(Maven) < 6.2.8; >= 6.3.0, < 6.3.2 6.2.8, 6.3.2 Fixed
crate = < 6.2.8; = >= 6.3.0, < 6.3.2 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
io.crate/crate(Maven) < 6.2.8 6.2.8
io.crate/crate(Maven) >= 6.3.0, < 6.3.2 6.3.2
crate = < 6.2.8 No fix listed
crate = >= 6.3.0, < 6.3.2 No fix listed

References