CVE-2026-75542
HighCVSS 8.3Exploitation Probability (EPSS)
Low risk29th percentile - higher than 29% of all known CVEs
Summary
An incorrect authorization vulnerability in the OAuth token endpoint in hexpm allows an API key with the repositories permission to read another organization's private packages. During key exchange for a token, scope validation does not resolve the organization name against the principal, and repository:<name> scope passes through unchanged. The token grants read access to that organization's private packages until expiration.
Risk Assessment
The organization may lose confidentiality of private packages if an API key with repositories permission is compromised or abused. An attacker can gain unauthorized access to other organizations' data.
Recommendation
Update hexpm to a version after 2026-08-24 that includes the fix. Additionally, restrict API key permissions and monitor OAuth token activity.
Other vulnerabilities in hexpm
See all- CVE-2026-75554Low
hexpm (hex.pm) has a vulnerability due to insufficient session expiration in the OAuth token refresh grant. A user removed from an organization can still read private packages because permission scopes are not properly updated. Affects hex.pm from 2025-10-10 before 2026-08-24.
- CVE-2026-23940Medium
In hexpm/hexpm before commit 495f01607d3eae4aed7ad09b2f54f31ec7a7df01 and hex.pm before 2026-03-10, an uncontrolled resource consumption vulnerability exists. Publishing an oversized package can cause memory exhaustion during tarball extraction, leading to denial of service.
- CVE-2026-21618Medium
hexpm (hex.pm) has a Cross-Site Scripting (XSS) vulnerability in the Elixir.HexpmWeb.SharedAuthorizationView module. The render_grouped_scopes/3 function does not sanitize input, allowing script injection.
Original NVD description (English source)
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.