← Back
CVE-2026-49989
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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 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.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in io.crate:crate. Attackers reach the vulnerable code path via `DELETE /_blobs/{table}/{digest}` without authentication.
📍 Affected scope
io.crate:crate — . Attack surface: DELETE /_blobs/{table}/{digest} / GET /_blobs/secret_blobs/ / PUT /_blobs/... / GET /_blobs/....
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.3.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `DELETE /_blobs/{table}/{digest}` requests with malformed payloads or SQL meta-characters. Run `grep -r 'io.crate:crate' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'io.crate:crate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.crate:crate` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt 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 があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade io.crate:crate to 6.3.2ステージング環境で 6.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against DELETE /_blobs/{table}/{digest} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.crate:crate
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.3.2"}]}]