Authorization Flaw in io.crate:crate (CVE-2026-49989)
Summary
Vulnerability in io.crate:crate (CVE-2026-49989). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /_blobs/{table}/{digest}. Mitigation: upgrade to 6.3.2 or later.
Original description
The description as published by the 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 GRANTs. CrateDB has two ways to access blob storage: SQL (SELECT ... FROM blob. 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/. 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49989 has been found in io.crate:crate.
Attackers can target a specific entry point like DELETE /_blobs/{table}/{digest} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade io.crate:crate to 6.3.2 or later.
If unsure, ask your IT team or search "io.crate:crate CVE-2026-49989" on the vendor's site.
CVE-2026-49989 (io.crate:crate) — CWE-863
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DELETE /_blobs/{table}/{digest} / GET /_blobs/secret_blobs/ / PUT /_blobs/... / GET /_blobs/...
Patched: 6.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in io.crate:crate. Attackers reach the vulnerable code path via DELETE /_blobs/{table}/{digest} without authentication.
Check the vendor advisory for the affected versions of io.crate:crate. Attack surface: DELETE /_blobs/{table}/{digest} / GET /_blobs/secret_blobs/ / PUT /_blobs/... / GET /_blobs/....
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual DELETE /_blobs/{table}/{digest} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.crate:crate を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'DELETE /_blobs/{table}/{digest}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /_blobs/{table}/{digest}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade io.crate:crate to 6.3.2ステージング環境で 6.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against DELETE /_blobs/{table}/{digest} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com