External risk intelligence

Hexpm Password Reset Tokens Do Not Expire Leading to Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.5)

CVE-2026-21622

The vulnerability exists in the hex.pm platform, which is a public-facing package registry and web application. As a centralized identity and account management service accessible over the internet for package management, it is designed to be public-facing by nature in its normal deployment.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability concerns an insufficient session expiration flaw in the Hexpm password reset system, where reset tokens do not expire, potentially allowing account takeover if historical emails are exposed.

  • Password reset links remain valid indefinitely.
  • Leaked past emails can enable account takeover.
  • Confirm relevance and exposure of affected systems.

Attack Path

How an attacker could exploit the issue

An attacker could gain unauthorized access to a user's account by exploiting an issue with how password reset tokens are handled. If a user's past emails are exposed, an attacker could use an old, unexpired password reset email to change the victim's password, even without current access to their email. This could lead to account takeover on the hex.pm platform.

  • Entry condition: Leaked password reset email.
  • Trigger point: Resending a password reset email.
  • Resulting risk: Account takeover.

Live Threat

Current exploitation, exposure, and threat context

Account takeover is a risk when previously issued password reset tokens are exposed through a data breach, as these tokens do not expire and remain valid indefinitely until used. This means an attacker could use a leaked password reset email to gain control of a user's account without needing current access to their email.

  • User account credentials.
  • Leaked emails could be exploited.
  • Unauthorized account access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The hexpm platform team is responsible for addressing this vulnerability. The first practical step is to identify all instances of the hexpm platform, confirm their reachability and business criticality, and then assign ownership for remediation planning.

  • Ownership: hexpm platform team.
  • Verify first: Exposed password reset tokens.
  • Action: Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the hexpm software and how is it used?

Hexpm is the core platform powering hex.pm, the primary package manager for the Erlang and Elixir programming ecosystems. Developers use this software to publish, discover, and manage code libraries. It functions as a centralized repository where users authenticate to secure their published packages, making account integrity critical for maintaining the software supply chain.

What does CWE-613 mean for CVE-2026-21622?

CWE-613 identifies an 'Insufficient Session Expiration' weakness. In this specific case, it means that tokens generated by the password reset system never time out. Because the application fails to invalidate these tokens after a reasonable period, a single password reset link remains a permanent key to an account, effectively bypassing the security controls intended to protect user sessions.

How does an attacker trigger this vulnerability?

An attacker needs access to a previously sent, unused password reset email, perhaps obtained through a historical data breach of the victim's email provider. The bug is triggered when that specific, long-expired token is submitted to the password reset flow. Notably, the vulnerability does not trigger if the user has already used the token or if no reset request was ever generated for that account.

Is my hexpm instance vulnerable according to Halo Surface Signal?

Yes, if you are running the affected software version. Halo Surface Signal notes that hex.pm is designed as a public-facing package registry. Because this infrastructure is inherently accessible over the internet to serve the developer community, any instance missing the necessary security updates is considered reachable and at increased risk of unauthorized account access.

What should I do if I run this technology?

First, confirm if your specific deployment falls within the affected version range. Because the fix requires changing how the application handles token lifecycles, you must prioritize identifying all instances of the platform in your environment. Once identified, coordinate with the platform owners to schedule the necessary software updates to ensure token expiration is properly enforced.

References