Team data disclosure via missing membership check
Published Sep 15, 2026 · Updated Sep 15, 2026
Missing authorization in Yao through 1.0.0-rc22 allows remote authenticated users to read sensitive team records via its OpenAPI endpoint. The GET /user/teams/:id handler authenticates the request but returns the full team record without verifying that the requester belongs to that team. A valid account and known team identifier are required; exposure is limited to team names, descriptions, owner details, and settings.
Summary
What happened
Missing authorization in Yao through 1.0.0-rc22 allows remote authenticated users to read sensitive team records via its OpenAPI endpoint. The GET /user/teams/:id handler authenticates the request but returns the full team record without verifying that the requester belongs to that team. A valid account and known team identifier are required; exposure is limited to team names, descriptions, owner details, and settings.
The record
- CVE
- CVE-2026-91774
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- YaoApp
- Product
- Yao
- Classifications
- T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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.0.0-rc22
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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