Auth bypass in Taubyte Tau
CVE-2026-69119
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.3 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H.
EPSS exploit prediction
EPSS: 0.005 (37.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 37th percentile — 37.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.005 · change: +0.001
Affected products
- Taubyte Tau — versions 0
Weakness classification (CWE)
References
- github.com/taubyte/tau (product)
- github.com/taubyte/tau/issues/513 (issue-tracking)
- github.com/taubyte/tau/commit/f5c9c9c311a1ff156814e0c81f186bfd101ec237 (patch)
- www.vulncheck.com/advisories/taubyte-tau-missing-authorization-via-post-project… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-69119?
- CVE-2026-69119 is a high-severity vulnerability in Taubyte Tau, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 8.3/10. Published 2026-08-11.
- How severe is CVE-2026-69119?
- High severity. CVSS v3 base score is 8.3 out of 10.