CVE-2026-24468

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3% (22nd 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-23883 (ENISA EUVD)Source: ENISA EUVD

5.3EG
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.3%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — 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.11.0 and prior to version 2.0.13, the /api/reset endpoint behaves differently depending on whether the supplied username exists in the system. When a non-existent email is provided in the login parameter, the endpoint returns an HTTP 400 response (Bad Request). When a valid email is supplied, the endpoint responds with HTTP 200. This difference in server responses creates an observable discrepancy that allows an attacker to reliably determine which emails are registered in the application. By automating requests with a list of possible email addresses, an attacker can quickly build a list of valid accounts without any authentication. The endpoint should return a consistent response regardless of whether the username exists in order to prevent account enumeration. Version 2.0.13 fixes this issue.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
22nd
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. 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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 20, 2026

Advisory Details (4)

Auto-updated Aug 3, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)

Username/Email Enumeration Through Differential HTTP Responses in Password Reset API · Advisory · OpenAEV-Platform/openaev · GitHub

https://github.com/OpenAEV-Platform/openaev/security/advisories/GHSA-v6rg-hf9w-f8ph
GitHub release Patch Available

Version 2.0.13

Patch available: OpenAEV-Platform/openaev 2.0.13

https://github.com/OpenAEV-Platform/openaev/releases/tag/2.0.13
GitHub commit

commit 3430fe23a924 (OpenAEV-Platform/openaev)

Fix landed in OpenAEV-Platform/openaev commit 3430fe23a924 — awaiting tagged release

https://github.com/OpenAEV-Platform/openaev/commit/3430fe23a9244030d06fdf8e6771592e1f12ad52
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 8× in last 7d / 37× 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 221 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 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-24468?
CVE-2026-24468 is a medium-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.11.0 and prior to version 2.0.13, the /api/reset endpoint behaves differently depending on whether the supplied username exists in the system.…
When was the CVE record for CVE-2026-24468 published?
The CVE record for CVE-2026-24468 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 20, 2026; the record at its source may have been updated since.
Is CVE-2026-24468 actively exploited?
CVE-2026-24468 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24468?
CVE-2026-24468 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-24468?
A fix for CVE-2026-24468 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-24468?

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