CVE-2026-82755
MEDIUMDescription
Use of Cache Containing Sensitive Information vulnerability in ash-project ash_authentication_oauth2_server allows a shared HTTP cache to serve one tenant's OAuth discovery metadata to another tenant's clients. The RFC 8414 and RFC 9728 metadata endpoints in AshAuthentication.Phoenix.Oauth2Server.ProtocolRouter return tenant-specific values (issuer, authorization_endpoint, token_endpoint, jwks_uri) when a tenant is set, but sent them with Cache-Control: public, max-age=3600 and no Vary. When the tenant is derived from something other than the URL (a header or the Host) and a shared cache sits in front, the cache key is the URL alone, so a stored response for one tenant is served to another for up to an hour. Affected clients may then send authorization codes and secrets to the wrong tenant's token endpoint and validate tokens against the wrong keys. This issue affects ash_authentication_oauth2_server: from 0.1.3 before 0.3.1.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 30% of all known CVEs.
References
Related Vulnerabilities
Other CWE-524 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-9494 | Medium | 5.9 | 3.9% | - | Fix |
| CVE-2021-24027 | High | 7.5 | 3.8% | - | Fix |
| CVE-2019-9495 | Low | 3.7 | 3.5% | - | Fix |
| CVE-2019-14997 | Medium | 4.3 | 1.2% | - | Fix |
| CVE-2024-0874 | Medium | 5.3 | 0.8% | - | Fix |
| CVE-2024-45596 | High | 7.4 | 0.7% | - | Fix |
Common questions
How do I fix CVE-2026-82755?
No published fix for CVE-2026-82755 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-82755 being actively exploited?
Not that we know of. CVE-2026-82755 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.37% is the estimated probability that it will be exploited in the next 30 days. That is higher than 30% of all scored CVEs.
How severe is CVE-2026-82755?
CVE-2026-82755 has a CVSS v4 base score of 6.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-82755
Markdown
[](https://tridentstack.com/cve/CVE-2026-82755)HTML
<a href="https://tridentstack.com/cve/CVE-2026-82755"><img src="https://tridentstack.com/cve/badge/CVE-2026-82755.svg" alt="CVE-2026-82755"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-08.