Explicit organization scopes survive token refresh after membership ends (CVE-2026-75554) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-75554

Explicit organization scopes survive token refresh after membership ends

Answer in brief

CVE-2026-75554 records a Unknown severity vulnerability in Explicit organization scopes survive token refresh after membership ends. 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.

Published Aug 24, 2026Updated Aug 24, 2026Source checked Aug 24, 2026First seen by HOL Aug 24, 2026Material review Aug 24, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps hexpm/hexpm (generic), hexpm/hexpm (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
hexpm/hexpmgeneric	>=2025-10-10 <2026-08-24	2026-08-24
hexpm/hexpmgeneric	>=650faa03af511e74c1b3b49ec12d35666b6984c4 <50cffd206490c49c92d7b63c8505949682abedb0	50cffd206490c49c92d7b63c8505949682abedb0

Recommended response

Check inventory. Check lockfiles and deployed manifests for hexpm/hexpm, hexpm/hexpm.
Review the reported fix. Update hexpm/hexpm to 2026-08-24; hexpm/hexpm to 50cffd206490c49c92d7b63c8505949682abedb0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 24, 2026

Sources and claim methodology

Upstream source description

Insufficient Session Expiration vulnerability in the OAuth token refresh grant in hexpm hexpm allows a user removed from an organization to keep reading its private packages. expand_repositories_scope/3 in lib/hexpm/permissions.ex only rewrites the literal repositories scope, so an explicitly granted repository:<org> or docs:<org> scope passes through it untouched. The refresh grant re-derives a new token from the stored granted_scopes, which holds that expanded form, so every refresh reproduces the organization scope without revisiting membership. Because both CDN edges authorize repository access from the token claim without querying the database, an account removed from an organization retains read access for as long as it keeps refreshing, bounded by the 30 day refresh token lifetime rather than the 30 minute access token lifetime. This issue affects hex.pm: from 2025-10-10 before 2026-08-24.

Quoted source text, attributed separately from HOL analysis.