Quick answers
- Is CVE-2026-75542 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75542 being exploited in the wild.
- How severe is CVE-2026-75542?
- Informational severity, with a CVSS score of 0, published 24 August 2026.
- Which products and versions are affected?
- Hex Hex.pm from 2025-10-18 before 2026-08-24.
- Is there a fix for CVE-2026-75542?
- A patch was published on 2026-08-24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75542 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-75542?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an incorrect authorization flaw in the OAuth client_credentials token exchange flow (lib/hexpm_web/controllers/api/oauth_controller.ex). The validate_scopes_against_key/2 function fails to validate the organization context of a requested scope; when an API key holds the repositories permission, any scope string beginning with "repository:" passes validation without verifying the organization name matches the key principal. The expand_repositories_scope/3 function only rewrites the literal repositories scope, leaving explicit repository:<name> requests unchanged. CDN edge nodes authorize repository access directly from the token claim without database validation, resulting in minted tokens with read access to an unintended organization's private packages until expiration. An attacker needs a valid API key with repositories permission; no network or user interaction bypass is required.
Affected products
- Hex Hex.pm from 2025-10-18 before 2026-08-24
Timeline
- 2026-08-24: disclosed
- 2026-08-24: patched