Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-82755Published 2026-09-07

CVE-2026-82755 — ash-project ash_authentication_oauth2_server

medium (derived)

As of 2026-09-08, CVE-2026-82755 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in ash-project ash_authentication_oauth2_server, CVSS v4.0 6.3, EPSS 0.3% (29.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-82755 as of 2026-09-08; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
6.3/10Medium (derived)
EPSS
0.3%Higher than 29.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.3/10Threadlinqs triage score
Published
Updated 2026-09-08
CVSS v4.0 6.3 (Medium, derived from score) · EPSS 0.3% (higher than 29.7% of all scored CVEs) · Priority 4.3/10 · Published 2026-09-07

Last updated:

What is CVE-2026-82755?

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.

The record classifies CVE-2026-82755 under weakness class CWE-524. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 28 days ago.

Severity and exploitation probability

CVSS v4.0 base score
6.3 — Medium (derived from score)
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
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 29.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-07, last modified 2026-09-08

Is CVE-2026-82755 being exploited?

It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-82755

No vendor patch reference has been recorded for CVE-2026-82755 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-82755

No threat campaign in the Threadlinqs corpus currently references CVE-2026-82755, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .

Vendor advisory and patch

Other references