Answer in brief
CVE-2026-75542 records a Unknown severity vulnerability in OAuth token exchange grants repository scopes for organizations the principal cannot access. The current sources do not mark it as known exploited. The current feed maps hexpm/hexpm (generic), hexpm/hexpm (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 hexpm/hexpm (generic), hexpm/hexpm (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| hexpm/hexpmgeneric | >=2025-10-18 <2026-08-24 | 2026-08-24 |
| hexpm/hexpmgeneric | >=71829cb6f6559bcceb1ef4e43a2fb8cdd3af654b <bf0fb9d208f0acfabf7a2f7467c8231659e322a8 | bf0fb9d208f0acfabf7a2f7467c8231659e322a8 |
Published upstream
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 24, 2026
Incorrect Authorization vulnerability in the OAuth token endpoint in hexpm hexpm allows an API key holding the repositories permission to read another organization's private packages. When an API key is exchanged for a token through the OAuth client_credentials grant, validate_scopes_against_key/2 in lib/hexpm_web/controllers/api/oauth_controller.ex admits a requested scope whenever the key carries the repositories permission and the scope string begins with repository:. The organization name is never resolved against the principal, and expand_repositories_scope/3 only rewrites the literal repositories scope, so an explicit repository:<name> passes through untouched. Both CDN edges authorize repository access from the token claim without querying the database, so the minted token is read access to that organization's private packages until it expires. This issue affects hex.pm: from 2025-10-18 before 2026-08-24.
Quoted source text, attributed separately from HOL analysis.