CVE-2026-69119: Authorization Bypass Through User-Controlled Key in Taubyte tau
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.
AI Analysis
Technical Summary
CVE-2026-69119 describes a missing authorization vulnerability in Taubyte Tau v1.1.10. The GitHubTokenHTTPAuth middleware validates only that a caller presents a valid GitHub OAuth token but fails to verify whether the token holder has ownership or access rights to the targeted project. This flaw allows any authenticated user to perform unauthorized read and delete operations on any tenant's project by invoking the GET and DELETE /projects/{id} endpoints with arbitrary project IDs. The vulnerability enables cross-tenant project takeover through bare KV-store operations such as projects.Fetch and project.Delete.
Potential Impact
An attacker with any valid GitHub OAuth token can read or permanently delete projects belonging to other tenants, resulting in unauthorized data access and potential data loss. This cross-tenant authorization bypass compromises tenant isolation and project integrity within the affected service.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected endpoints and monitor for unauthorized use of GitHub OAuth tokens. Implement additional authorization checks to verify project ownership or access rights before allowing project operations.
CVE-2026-69119: Authorization Bypass Through User-Controlled Key in Taubyte tau
Description
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.
CVSS v4.0
Score 7.2high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-69119 describes a missing authorization vulnerability in Taubyte Tau v1.1.10. The GitHubTokenHTTPAuth middleware validates only that a caller presents a valid GitHub OAuth token but fails to verify whether the token holder has ownership or access rights to the targeted project. This flaw allows any authenticated user to perform unauthorized read and delete operations on any tenant's project by invoking the GET and DELETE /projects/{id} endpoints with arbitrary project IDs. The vulnerability enables cross-tenant project takeover through bare KV-store operations such as projects.Fetch and project.Delete.
Potential Impact
An attacker with any valid GitHub OAuth token can read or permanently delete projects belonging to other tenants, resulting in unauthorized data access and potential data loss. This cross-tenant authorization bypass compromises tenant isolation and project integrity within the affected service.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected endpoints and monitor for unauthorized use of GitHub OAuth tokens. Implement additional authorization checks to verify project ownership or access rights before allowing project operations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-03T13:26:21.234Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7b7424bf8831d539467fd3
Added to database: 08/11/2026, 19:12:36 UTC
Last enriched: 08/11/2026, 19:26:18 UTC
Last updated: 08/12/2026, 01:03:22 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.