CVE-2026-69119

Taubyte Tau v1.1.10 Missing Authorization via GET and DELETE /projects/{id}

Published Aug 11, 2026 CVSS 4.0 · 7.2 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in the services/auth HTTP service of Taubyte Tau v1.1.10. A caller merely needs a valid GitHub OAuth token; the middleware only verifies the token and does not confirm that the token holder owns or has rights to the requested project. Consequently an attacker can read or permanently delete any project belonging to other tenants by sending GET or DELETE requests to /projects/{id}. This flaw permits cross‑tenant data compromise and deletion, essentially enabling an adversary to control another tenant’s project. The weakness corresponds to CWE‑639, Unauthorized Information Disclosure/Privilege Management. The attacker can execute destructive actions without needing administrative privileges on the target environment.

Affected Systems

Taubyte tau (v1.1.10) running the services/auth HTTP endpoint. Any deployment of this version under a user that authenticates with a valid GitHub OAuth token is susceptible. The flaw appears in the authentication layer that is shared by all tenants.

Risk and Exploitability

The CVSS base score is 7.2, indicating a high severity impact and medium complexity of exploitation. The EPSS score is below 1%, suggesting a very low probability of current exploitation, and the flaw is not listed in CISA’s KEV catalog. Nevertheless, the issue can be leveraged by any authenticated user with a GitHub token, making it relatively easy to exploit once the attacker has a token. The direct attack path is a simple HTTP request to a known endpoint, and no additional privileges are required beyond token possession.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Deploy the latest Taubyte tau release that addresses the missing authorization check for project endpoints.
  • Re‑configure the GitHub OAuth integration to verify project ownership or restrict token scopes to avoid granting permission to unrelated projects.
  • Audit existing projects for unauthorized deletions and restore data from backups if necessary.

Generated by OpenCVE AI on August 12, 2026 at 20:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Taubyte Tau v1.1.10 Missing Authorization via POST /projects/{id} Taubyte Tau v1.1.10 Missing Authorization via GET and DELETE /projects/{id}
Type Values Removed Values Added
First Time appeared Taubyte
Taubyte tau
Vendors & Products Taubyte
Taubyte tau
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Taubyte Tau v1.1.10 Missing Authorization via POST /projects/{id}
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H'}

cvssV4_0

{'score': 7.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 29, 2026, 9:16 PM
Reserved
Aug 3, 2026, 1:26 PM
Status
Deferred
Published
Aug 11, 2026, 7:18 PM
Modified
Oct 24, 2026, 4:10 PM