CVE-2026-75542

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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: 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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 25, 2026

Advisory Details (4)

Auto-updated Aug 24, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit bf0fb9d208f0 (hexpm/hexpm)

Fix landed in hexpm/hexpm commit bf0fb9d208f0 — awaiting tagged release

https://github.com/hexpm/hexpm/commit/bf0fb9d208f0acfabf7a2f7467c8231659e322a8
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-75542
github Patch Available🟡 PoC Available

OAuth token exchange grants repository scopes for organizations the principal cannot access · Advisory · hexpm/hexpm · GitHub

https://github.com/hexpm/hexpm/security/advisories/GHSA-rfx8-w654-8cpr

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 00:21 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 20:45 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 20:45 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-26 08:25 UTCEG score recompute
  9. 2026-08-25 20:24 UTCEG score recompute
  10. 2026-08-25 20:01 UTCEG score recompute
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 21:26 UTCEG score recompute
  13. 2026-08-24 20:26 UTCEG score recompute
  14. 2026-08-24 20:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75542?
CVE-2026-75542 is a high vulnerability published on August 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 clientcredentials grant, validatescopesagainstkey/2 in…
When was CVE-2026-75542 disclosed?
CVE-2026-75542 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75542 actively exploited?
CVE-2026-75542 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.0% of all scored CVEs.
What is the CVSS score of CVE-2026-75542?
CVE-2026-75542 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-75542?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75542, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75542

Explore →

Is Your Infrastructure Affected by CVE-2026-75542?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.