CVE-2026-49989
HighCVSS 7.1Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
CrateDB before versions 6.2.8 and 6.3.2 has a vulnerability that allows any authenticated user to read, delete, or add arbitrary blobs in any blob table, regardless of grants. The issue affects the HTTP API path, which does not check privileges via AccessControl, unlike the SQL path.
Risk Assessment
The organization is exposed to unauthorized access to data stored in blob tables, potentially leading to data leakage or loss.
Recommendation
It is recommended to immediately upgrade CrateDB to versions 6.2.8 or 6.3.2, which fix this vulnerability.
Original NVD description (English source)
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.