Cross-tenant project disclosure and deletion via unchecked IDs
Published Aug 11, 2026 · Updated Aug 11, 2026
Missing authorization in Taubyte Tau 1.1.10 allows remote authenticated users to read or delete another tenant's project by ID. The GET and DELETE handlers fetch or delete records using the path-supplied project ID without checking the caller's access to either linked repository. Any valid GitHub OAuth token passes the middleware, but exploitation also requires a known project ID; deletion is permanent through this API.
Summary
What happened
Missing authorization in Taubyte Tau 1.1.10 allows remote authenticated users to read or delete another tenant's project by ID. The GET and DELETE handlers fetch or delete records using the path-supplied project ID without checking the caller's access to either linked repository. Any valid GitHub OAuth token passes the middleware, but exploitation also requires a known project ID; deletion is permanent through this API.
The record
- CVE
- CVE-2026-69119
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Taubyte
- Product
- Tau
- Classifications
- CWE-639, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo