Answer in brief
CVE-2026-86698 records a Low severity (CVSS 2.3) vulnerability in Refresh tokens accepted as private repository credentials at the CDN. 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.
CVSS is 2.3. 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-10 <2026-09-22 | 2026-09-22 |
| hexpm/hexpmgeneric | >=650faa03af511e74c1b3b49ec12d35666b6984c4 <db58cf3a86c7639708ef52ff86de0b4f938e6360 | db58cf3a86c7639708ef52ff86de0b4f938e6360 |
Published upstream
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 22, 2026
Insufficient Session Expiration vulnerability in OAuth token issuance in hexpm hexpm allows a user whose organization membership or session has ended to keep reading the organization's private packages and their documentation tarballs via a retained refresh token. generate_refresh_token/4 in lib/hexpm/oauth/jwt.ex signs the refresh token with the same iss, aud and scope claims as the access token, so it carries the same repository:<org> scopes. The CDN service that serves private repositories verifies the signature and time claims and then authorizes from the scope claim, with no database lookup and no way to tell the two token kinds apart. Removing a member or revoking a session therefore takes effect at the CDN only when the 30 day refresh token expires, instead of after the 30 minute access token lifetime. Access is read-only and limited to organizations the account belonged to when the token was granted. This issue affects hex.pm: from 2025-10-10 before 2026-09-22.
Quoted source text, attributed separately from HOL analysis.