Authenticated blob access via missing HTTP authorization check
Published Aug 14, 2026 · Updated Aug 14, 2026
Incorrect authorization in CrateDB before 6.2.8 and 6.3.0 through 6.3.1 allows remote authenticated users to read, delete, or plant blobs. HttpBlobHandler dispatches GET, HEAD, PUT, and DELETE requests directly to blob operations without consulting AccessControl for table privileges. A reachable BLOB TABLE and valid account are required; reading or deleting an existing blob also requires its SHA-1 digest, while planting a new blob does not.
Summary
What happened
Incorrect authorization in CrateDB before 6.2.8 and 6.3.0 through 6.3.1 allows remote authenticated users to read, delete, or plant blobs. HttpBlobHandler dispatches GET, HEAD, PUT, and DELETE requests directly to blob operations without consulting AccessControl for table privileges. A reachable BLOB TABLE and valid account are required; reading or deleting an existing blob also requires its SHA-1 digest, while planting a new blob does not.
The record
- CVE
- CVE-2026-49989
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- Crate.io
- Product
- CrateDB
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.2.8
- Affected versionversion=>= 6.3.0, < 6.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- End-to-end Docker proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo