CVE-2026-21622
Insufficient Session Expiration in Hexpm Password Reset Enables Account Takeover
Publication date: 2026-03-05
Last updated on: 2026-04-06
Assigner: EEF
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| hex | hexpm | From 2025-10-01 (inc) to 2026-03-05 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-613 | According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Insufficient Session Expiration issue in the hexpm hexpm system, specifically in the 'Elixir.Hexpm.Accounts.PasswordReset' module. Password reset tokens generated during the "Reset your password" process do not expire over time. When a user requests a password reset, Hex sends an email with a reset link containing a token that remains valid indefinitely until it is used.
Because these tokens never expire, if an attacker gains access to a user's old emails (for example, through a data breach or leaked mailbox archive), they can use any unused password reset email to reset the victim's password. The attacker does not need current access to the victim's email account, only access to a previously leaked copy of the reset email.
How can this vulnerability impact me? :
This vulnerability can lead to an account takeover. An attacker who obtains a previously leaked password reset email can reset the victim's password and gain unauthorized access to their account. This compromises the security and privacy of the affected user's account and any sensitive data or services associated with it.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know