Am I affected?

This record states its affected versions in a form that can't be compared automatically.

617e44c < bb0e420 affected
every other version: unaffected

Description

Insufficient Session Expiration vulnerability in hexpm hexpm/hexpm ('Elixir.Hexpm.Accounts.PasswordReset' module) allows Account Takeover.

Password reset tokens generated via the "Reset your password" flow do not expire. When a user requests a password reset, Hex sends an email containing a reset link with a token. This token remains valid indefinitely until used. There is no time-based expiration enforced.

If a user's historical emails are exposed through a data breach (e.g., a leaked mailbox archive), any unused password reset email contained in that dataset could be used by an attacker 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.

This vulnerability is associated with program files lib/hexpm/accounts/password_reset.ex and program routines 'Elixir.Hexpm.Accounts.PasswordReset':can_reset?/3.

This issue affects hexpm: from 617e44c71f1dd9043870205f371d375c5c4d886d before bb0e42091995945deef10556f58d046a52eb7884.

Weaknesses & attack patterns

Weakness

CWE-613 · Insufficient Session Expiration in catalog → MITRE ↗

Attack patterns

CAPEC-21 · Exploitation of Trusted Identifiers MITRE ↗

CAPEC-21 Exploitation of Session Variables, Resource IDs and other Trusted Credentials

Affected — GitHub / hexpm/hexpm Repository ↗

617e44c < bb0e420 affected
every other version: unaffected
default status unaffected
cpe cpe:2.3:a:hexpm:hexpm:*:*:*:*:*:*:*:*
modules · source files · routines
modules 'Elixir.Hexpm.Accounts.PasswordReset'
source files lib/hexpm/accounts/password_reset.ex
routines 'Elixir.Hexpm.Accounts.PasswordReset':can_reset?/3

Affected — hexpm / hex.pm

2025-08-01 < 2026-03-05 affected
every other version: unaffected
default status unaffected

Workarounds

Users who suspect email exposure should:

  • Immediately reset their password.
  • Enable and enforce 2FA.

There is no complete mitigation without implementing token expiration.

References

Credits

Michael Lubas / Paraxial.io Finder
Jonatan Männchen / EEF Remediation developer
Eric Meadows-Jönsson / Hex.pm Remediation reviewer

CVSS breakdown

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L
« All CVEs