CVE-2026-56450

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

AIL did not restrict repeated failed attempts to verify a two-factor authentication (OTP) code. An attacker who had reached the 2FA verification step, such as after successfully completing the password-authentication stage, could submit an unlimited number of OTP guesses. This could enable brute-force guessing of a valid code and bypass the intended second authentication factor, resulting in unauthorized account access.

The patch introduces per-user failed-OTP tracking, blocks verification after 30 failed attempts for one hour, clears the counter after a successful OTP verification, and provides administrator recovery actions to purge affected lockouts.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
44.0%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit d3a394fe68fd (ail-project/ail-framework)

Patch available: ail-project/ail-framework v6.9 (contains commit d3a394fe68fd)

https://github.com/ail-project/ail-framework/commit/d3a394fe68fd5aeee86f3a3c91d4a0350f91e974

Vendor Advisories for CVE-2026-56450(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:20 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 18:58 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-15 19:29 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 21:25 UTCGHSA enrichment
  19. 2026-07-13 23:21 UTCGHSA enrichment
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 01:13 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-12 03:09 UTCGHSA enrichment
Show 52 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 04:59 UTCGHSA enrichment
  4. 2026-07-10 06:55 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 08:51 UTCGHSA enrichment
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 10:47 UTCGHSA enrichment
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 12:44 UTCGHSA enrichment
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 14:40 UTCGHSA enrichment
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 16:34 UTCGHSA enrichment
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 18:30 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 20:26 UTCGHSA enrichment
  26. 2026-07-02 22:23 UTCGHSA enrichment
  27. 2026-07-02 00:19 UTCGHSA enrichment
  28. 2026-07-01 15:07 UTCEPSS rescore
  29. 2026-07-01 02:16 UTCGHSA enrichment
  30. 2026-06-30 23:22 UTCEPSS rescore
  31. 2026-06-30 04:11 UTCGHSA enrichment
  32. 2026-06-29 14:06 UTCEPSS rescore
  33. 2026-06-29 06:08 UTCGHSA enrichment
  34. 2026-06-28 14:07 UTCEPSS rescore
  35. 2026-06-28 08:04 UTCGHSA enrichment
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-27 10:00 UTCGHSA enrichment
  39. 2026-06-27 03:08 UTCEPSS rescore
  40. 2026-06-26 11:56 UTCGHSA enrichment
  41. 2026-06-25 13:53 UTCGHSA enrichment
  42. 2026-06-25 13:49 UTCEPSS rescore
  43. 2026-06-24 15:49 UTCGHSA enrichment
  44. 2026-06-24 14:05 UTCEPSS rescore
  45. 2026-06-23 21:33 UTCEPSS rescore
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-23 17:46 UTCGHSA enrichment
  48. 2026-06-22 19:40 UTCEG score recompute▲ 5.10
  49. 2026-06-22 19:40 UTCGHSA enrichment
  50. 2026-06-22 19:39 UTCNVD updateCVSS v3 → 5.1 · CVSS v4 → 5.1
  51. 2026-06-22 15:37 UTCEG score recompute
  52. 2026-06-22 15:37 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56450?
CVE-2026-56450 is a medium vulnerability published on June 22, 2026. AIL did not restrict repeated failed attempts to verify a two-factor authentication (OTP) code. An attacker who had reached the 2FA verification step, such as after successfully completing the password-authentication stage, could submit an unlimited number of OTP guesses. This could enable…
When was CVE-2026-56450 disclosed?
CVE-2026-56450 was first published in the National Vulnerability Database on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56450 actively exploited?
CVE-2026-56450 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56450?
CVE-2026-56450 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-56450?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56450, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56450?

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

Start Free Scan →Browse All CVEs