CVE-2026-21621
Last modified
CVE-2026-21621 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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. EPSS estimates a 0.32% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Hex | Hexpm | >= 2025-10-17, < 2026-03-05 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-21621?
How severe is CVE-2026-21621?
How do I fix CVE-2026-21621?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-2160A vulnerability has been found in SourceCodester Simple Resp…6.1
- CVE-2026-2161A vulnerability was found in itsourcecode Directory Manageme…9.8
- CVE-2026-21618Improper Neutralization of Input During Web Page Generation …6.1
- CVE-2026-21619Uncontrolled Resource Consumption, Deserialization of Untrus…7.5
- CVE-2026-2162A vulnerability was determined in itsourcecode News Portal P…7.2
- CVE-2026-21620Relative Path Traversal, Improper Isolation or Compartmental…2.3
- CVE-2026-21622Insufficient Session Expiration vulnerability in hexpm hexpm…9.8
- CVE-2026-21623Lack of input filterung leads to a persistent XSS vulnerabil…5.4
- CVE-2026-21624Lack of input filterung leads to a persistent XSS vulnerabil…5.4
- CVE-2026-21625User provided uploads to the Easy Discuss component for Joom…8.8
- CVE-2026-21626Access control settings for forum post custom fields are not…7.5
- CVE-2026-21627The vulnerability was rooted in how the Tassos Framework plu…9.5
Are you affected by CVE-2026-21621?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
