CVE-2026-24467

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-23882 (ENISA EUVD)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

OpenAEV is an open source platform allowing organizations to plan, schedule and conduct cyber adversary simulation campaign and tests. Starting in version 1.0.0 and prior to version 2.0.13, OpenAEV's password reset implementation contains multiple security weaknesses that together allow reliable account takeover. The primary issue is that password reset tokens do not expire. Once a token is generated, it remains valid indefinitely, even if significant time has passed or if newer tokens are issued for the same account. This allows an attacker to accumulate valid password reset tokens over time and reuse them at any point in the future to reset a victim’s password. A secondary weakness is that password reset tokens are only 8 digits long. While an 8-digit numeric token provides 100,000,000 possible combinations (which is secure enough), the ability to generate large numbers of valid tokens drastically reduces the required number of attempts to guess a valid password reset token. For example, if an attacker generates 2,000 valid tokens, the brute-force effort is reduced to approximately 50,000 attempts, which is a trivially achievable number of requests for an automated attack. (100 requests per second can mathematically find a valid password reset token in 500 seconds.) By combining these flaws, an attacker can mass-generate valid password reset tokens and then brute-force them efficiently until a match is found, allowing the attacker to reset the victim’s password to a value of their choosing. The original password is not required, and the attack can be performed entirely without authentication. This vulnerability enables full account takeover that leads to platform compromise. An unauthenticated remote attacker can reset the password of any registered user account and gain complete access without authentication. Because user email addresses are exposed to other users by design, a single guessed or observed email address is sufficient to compromise even administrator accounts with non-guessable email addresses. This design flaw results in a reliable and scalable account takeover vulnerability that affects any registered user account in the system. Note: The vulnerability does not require OpenAEV to have the email service configured. The exploit does not depend on the target email address to be a real email address. It just needs to be registered to OpenAEV. Successful exploitation allows an unauthenticated remote attacker to access sensitive data (such as the Findings section of a simulation), modify payloads executed by deployed agents to compromise all hosts where agents are installed (therefore the Scope is changed). Users should upgrade to version 2.0.13 to receive a fix.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 20, 2026

Last Modified

April 25, 2026

Advisory Details (4)

Auto-updated May 2, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Improper Password Reset Token Management Leads to Unauthenticated Account Takeover and Platform Compromise · Advisory · OpenAEV-Platform/openaev · GitHub

https://github.com/OpenAEV-Platform/openaev/security/advisories/GHSA-vcjx-vw28-25p2
Web page

Release Version 2.0.13 · OpenAEV-Platform/openaev · GitHub

https://github.com/OpenAEV-Platform/openaev/releases/tag/2.0.13
Web page

[api/front] Be able to reset the password through a link on the login… · OpenAEV-Platform/openaev@c09a4e7 · GitHub

https://github.com/OpenAEV-Platform/openaev/commit/c09a4e71ea76d26fc28c9b51c76bca89a902df4f
Web page

openaev/openaev-api/src/main/java/io/openaev/rest/user/UserApi.java at 82fa7d0009017110c9b509d0dc1b3a78164259dd · OpenAEV-Platform/openaev · GitHub

https://github.com/OpenAEV-Platform/openaev/blob/82fa7d0009017110c9b509d0dc1b3a78164259dd/openaev-api/src/main/java/io/openaev/rest/user/UserApi.java#L120

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 249 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-02 02:46 UTCEG score recompute
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  4. 2026-11-01 03:48 UTCEG score recompute
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  6. 2026-10-31 04:49 UTCEG score recompute
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-10-30 05:50 UTCEG score recompute
  9. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  10. 2026-10-29 06:51 UTCEG score recompute
  11. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  12. 2026-10-28 07:51 UTCEG score recompute
  13. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-10-27 08:52 UTCEG score recompute
  15. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  16. 2026-10-26 08:21 UTCEG score recompute
  17. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  18. 2026-10-25 14:40 UTCEG score recompute
  19. 2026-10-25 09:22 UTCEG score recompute
  20. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-10-24 10:23 UTCEG score recompute
  22. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-10-23 11:24 UTCEG score recompute
  24. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  25. 2026-10-22 12:24 UTCEG score recompute
Show 74 more
  1. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-10-21 13:24 UTCEG score recompute
  3. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  4. 2026-10-20 14:19 UTCEG score recompute
  5. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  6. 2026-10-19 13:22 UTCEG score recompute
  7. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-18 03:53 UTCEG score recompute
  9. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-17 13:46 UTCEG score recompute
  11. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-10-16 14:45 UTCEG score recompute
  13. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-10-15 15:45 UTCEG score recompute
  15. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-14 09:59 UTCEG score recompute
  17. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-13 08:03 UTCEG score recompute
  19. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-12 16:20 UTCEG score recompute
  21. 2026-10-11 20:02 UTCEG score recompute
  22. 2026-10-11 17:15 UTCEG score recompute
  23. 2026-10-11 14:47 UTCEG score recompute
  24. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  25. 2026-10-11 04:31 UTCOSV refresh
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  27. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  28. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  29. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  30. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  31. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  32. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  33. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  34. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  35. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  36. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  37. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  38. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  39. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  40. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  41. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  42. 2026-09-21 16:19 UTCOSV refresh
  43. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  44. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  45. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  46. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  47. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  48. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  49. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  50. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  51. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  52. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  53. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  54. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  55. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  56. 2026-09-02 13:26 UTCOSV refresh
  57. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  58. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  59. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  60. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  61. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  62. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  63. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  64. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  66. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  67. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  68. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  69. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  70. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  71. 2026-08-16 06:24 UTCEG score recompute
  72. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  73. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  74. 2026-08-14 04:33 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-24467?
CVE-2026-24467 is a critical-severity vulnerability; its CVE record was published on April 20, 2026. OpenAEV is an open source platform allowing organizations to plan, schedule and conduct cyber adversary simulation campaign and tests. Starting in version 1.0.0 and prior to version 2.0.13, OpenAEV's password reset implementation contains multiple security weaknesses that together allow reliable…
When was the CVE record for CVE-2026-24467 published?
The CVE record for CVE-2026-24467 was published on April 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 25, 2026; the record at its source may have been updated since.
Is CVE-2026-24467 actively exploited?
CVE-2026-24467 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24467?
CVE-2026-24467 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-24467?
The CVE record for CVE-2026-24467 names the fix: "Users should upgrade to version 2.0.13 to receive a fix."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-24467

Explore →

Is Your Infrastructure Affected by CVE-2026-24467?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.