Vulnerability in Taubyte Tau (CVE-2026-69119)
Summary
Vulnerability in Taubyte Tau (CVE-2026-69119). Data can be tampered with by attackers. Exploitable via DELETE /projects/{id}.
Original description
The description as published by the source.
Taubyte Tau v1.1.10 contains a missing authorization vulnerability in the services/auth HTTP service that allows any authenticated user to read or permanently delete another tenant's project by supplying an arbitrary project ID to the GET and DELETE /projects/{id} endpoints. The GitHubTokenHTTPAuth middleware only validates that a caller presents a valid GitHub OAuth token without verifying ownership or access rights to the target project, enabling attackers with any valid GitHub token to invoke bare KV-store operations such as projects.Fetch and project.Delete against any project ID to achieve cross-tenant project takeover.
Source: NIST National Vulnerability Database 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-69119 has been found in Taubyte Tau.
Attackers can target a specific entry point like DELETE /projects/{id} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Taubyte Tau CVE-2026-69119" on the vendor's site.
CVE-2026-69119 (Taubyte Tau) — CWE-639 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /projects/{id}
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.
A vulnerability (CWE-639) exists in Taubyte Tau. Attackers reach the vulnerable code path via DELETE /projects/{id}.
Check the vendor advisory for the affected versions of Taubyte Tau. Attack surface: DELETE /projects/{id}.
Severity: High (CVSS 8.3/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
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 /projects/{id} 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・依存マニフェストで Taubyte Tau を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'DELETE /projects/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /projects/{id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against DELETE /projects/{id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。