Cross-tenant OAuth confusion via publicly cached metadata
Published Sep 7, 2026 · Updated Sep 8, 2026
Cache isolation failure in Ash Project ash_authentication_oauth2_server 0.1.3 through 0.3.0 allows remote attackers to confuse OAuth clients. ProtocolRouter marks tenant-specific discovery responses public for one hour without varying on a header- or Host-derived tenant, allowing a shared cache to reuse one tenant's issuer, endpoints, and key URI for another. Exposure requires a multi-tenant deployment behind such a cache and can direct authorization codes or client secrets to the wrong tenant and cause token validation against the wrong keys.
Summary
What happened
Cache isolation failure in Ash Project ash_authentication_oauth2_server 0.1.3 through 0.3.0 allows remote attackers to confuse OAuth clients. ProtocolRouter marks tenant-specific discovery responses public for one hour without varying on a header- or Host-derived tenant, allowing a shared cache to reuse one tenant's issuer, endpoints, and key URI for another. Exposure requires a multi-tenant deployment behind such a cache and can direct authorization codes or client secrets to the wrong tenant and cause token validation against the wrong keys.
The record
- CVE
- CVE-2026-82755
- Published
- Sep 7, 2026
- Updated
- Sep 8, 2026
- Vendor
- Ash Project
- Product
- ash_authentication_oauth2_server
- Classifications
- CWE-524, CAPEC-204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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.3 <0.3.1
- Affected versionversion=99de0a1cacb5ef667c4533278b7c81ca98c00231 <768d87f70e4e97ae1d2bf1606b5bf3f4d03f24a1
What conditions does exploitation require?
What is affected?
Published CVSS scores
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