Skip to content
Applications

CVE-2026-73431

8.8
High
EPSS 0.28%Patch availableAug 13, 2026

Replayable activation/recovery tokens enable account takeover during token validity.

common questions

Is CVE-2026-73431 being exploited?

Not confirmed. CVE-2026-73431 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-73431?

CVE-2026-73431 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73431?

Yes. A fix has been recorded for CVE-2026-73431. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73431 affect?

CVE-2026-73431 affects Vulnerability-Lookup deployments using stateless activation/recovery tokens. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73431?

Apply vendor patch to enforce purpose-bound, single-use tokens and invalidate previous tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Vulnerability-Lookup deployments using stateless activation/recovery tokens
impact

Capture of an activation/recovery link allows repeated password resets and account takeover without knowing credentials.

action required

Immediate action required

affected versions
vulnerability-lookup vulnerability-lookup
  • affected<= 5.5.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free