CVE-2026-21621: Improper Scope Enforcement in OAuth client_credentials Flow Allows Read-Only API Key to Escalate to Full Access

Published Mar 5, 2026
·
Updated

Incorrect Authorization vulnerability in hexpm hexpm/hexpm ('Elixir.HexpmWeb.API.OAuthController' module) allows Privilege Escalation. An API key created with read-only permissions (domain: "api", resource: "read") can be escalated to full write access under specific conditions. When exchanging a read-only API key via the OAuth client_credentials grant, the resource qualifier is ignored. The resulting JWT receives the broad "api" scope instead of the expected "api:read" scope. This token is therefore treated as having full API access. If an attacker is able to obtain a victim's read-only API key and a valid 2FA (TOTP) code for the victim account, they can use the incorrectly scoped JWT to create a new full-access API key with unrestricted API permissions that does not expire by default and can perform write operations such as publishing, retiring, or modifying packages. This vulnerability is associated with program files lib/hexpm_web/controllers/api/oauth_controller.ex and program routines 'Elixir.HexpmWeb.API.OAuthController':validate_scopes_against_key/2. This issue affects hexpm: from 71829cb6f6559bcceb1ef4e43a2fb8cdd3af654b before 71c127afebb7ed7cc637eb231b98feb802d62999.

Affected Software

2 affected components
hexpm/hexpm>71829cb6f6559bcceb1ef4e43a2fb8cdd3af654b<=71c127afebb7ed7cc637eb231b98feb802d62999
Hex hexpm>=2025-10-17<2026-03-05

Event History

Mar 5, 2026
CVE Published
via MITRE·07:20 PM
Data Sourced
via MITRE·07:20 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21621?

CVE-2026-21621 is considered to be a high severity vulnerability due to the potential for privilege escalation.

2

How does CVE-2026-21621 affect API key permissions?

CVE-2026-21621 allows a read-only API key to escalate to full access permissions, compromising security.

3

Which software versions are impacted by CVE-2026-21621?

CVE-2026-21621 affects hexpm/hexpm versions between 71829cb6f6559bcceb1ef4e43a2fb8cdd3af654b and 71c127afebb7ed7cc637eb231b98feb802d62999.

4

How can I mitigate the issues caused by CVE-2026-21621?

To mitigate CVE-2026-21621, ensure that API keys are correctly scoped and restrict their permissions appropriately.

5

What component of the hexpm application is vulnerable in CVE-2026-21621?

The vulnerability in CVE-2026-21621 is found in the Elixir.HexpmWeb.API.OAuthController module.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203