Answer in brief
CVE-2026-82754 records a Unknown severity vulnerability in ash_authentication_oauth2_server aliases every protocol endpoint under /.well-known, bypassing path-scoped controls. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_authentication_oauth2_server (generic), ash-project/ash_authentication_oauth2_server (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash_authentication_oauth2_server (generic), ash-project/ash_authentication_oauth2_server (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash_authentication_oauth2_servergeneric | >=0.1.0 <0.3.1 | 0.3.1 |
| ash-project/ash_authentication_oauth2_servergeneric | >=855b578037c5ded18e8a6e60f42e56bde4905fae <a72972d7ed3eb74c05dfa0653a258ef14454459a | a72972d7ed3eb74c05dfa0653a258ef14454459a |
Published upstream
Sep 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 7, 2026
Improper Protection of Alternate Path vulnerability in ash-project ash_authentication_oauth2_server exposes the state-changing OAuth endpoints under an unintended URL prefix, bypassing controls scoped to the canonical prefix. oauth2_server_protocol_routes/1 in AshAuthentication.Phoenix.Oauth2Server.Router forwards the same ProtocolRouter at both the /oauth prefix and the /.well-known prefix. Phoenix forward strips the matched prefix before dispatch, so the full route table answers under both mounts, and POST /register, POST /token, and POST /revoke are reachable as /.well-known/register, /.well-known/token, and /.well-known/revoke. Edge controls such as WAF rules, rate limits, or authentication exemptions written against the /oauth paths, or that allow-list /.well-known as unauthenticated, do not apply to the alias. This issue affects ash_authentication_oauth2_server: from 0.1.0 before 0.3.1.
Quoted source text, attributed separately from HOL analysis.