CVE-2026-45413

MEDIUMNVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 100% 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, nvd
Trending — 3 sources updated this week
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

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

MaxKB is an open-source AI assistant for enterprise. Prior to 2.9.1, user passwords are stored using unsalted MD5 hashes, making them trivially crackable via rainbow tables or GPU-accelerated brute force (hashcat). This vulnerability is fixed in 2.9.1.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity69% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.3%
KEV
Not listed

Published

May 26, 2026

Last Modified

May 27, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
Patch available. Sources: github.
github Patch Available

Unsalted MD5 Password Hashing · Advisory · 1Panel-dev/MaxKB · GitHub

https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-2m4c-mcq5-q8xq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 22× 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-23 03:16 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 05:52 UTCOSV refresh
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
Show 29 more
  1. 2026-06-15 17:49 UTCEPSS rescore
  2. 2026-06-13 23:00 UTCEPSS rescore
  3. 2026-06-12 23:12 UTCEPSS rescore
  4. 2026-06-12 23:12 UTCEPSS rescore
  5. 2026-06-11 14:00 UTCEPSS rescore
  6. 2026-06-10 22:18 UTCEPSS rescore
  7. 2026-06-08 14:17 UTCEPSS rescore
  8. 2026-06-08 14:17 UTCEPSS rescore
  9. 2026-06-07 15:25 UTCEPSS rescore
  10. 2026-06-07 15:25 UTCEPSS rescore
  11. 2026-06-06 13:47 UTCEPSS rescore
  12. 2026-06-06 13:47 UTCEPSS rescore
  13. 2026-06-05 22:47 UTCEPSS rescore
  14. 2026-06-04 13:12 UTCEPSS rescore
  15. 2026-06-04 13:12 UTCEPSS rescore
  16. 2026-06-02 20:13 UTCEPSS rescore
  17. 2026-06-01 13:52 UTCEPSS rescore
  18. 2026-06-01 13:52 UTCEPSS rescore
  19. 2026-05-31 22:30 UTCEPSS rescore
  20. 2026-05-31 22:30 UTCEPSS rescore
  21. 2026-05-31 00:16 UTCEPSS rescore
  22. 2026-05-31 00:16 UTCEPSS rescore
  23. 2026-05-29 13:44 UTCEPSS rescore
  24. 2026-05-29 13:44 UTCEPSS rescore
  25. 2026-05-28 13:44 UTCEPSS rescore
  26. 2026-05-28 13:44 UTCEPSS rescore
  27. 2026-05-27 13:40 UTCEPSS rescore
  28. 2026-05-27 13:40 UTCEPSS rescore
  29. 2026-05-26 20:29 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45413?
CVE-2026-45413 is a medium vulnerability published on May 26, 2026. MaxKB is an open-source AI assistant for enterprise. Prior to 2.9.1, user passwords are stored using unsalted MD5 hashes, making them trivially crackable via rainbow tables or GPU-accelerated brute force (hashcat). This vulnerability is fixed in 2.9.1.
When was CVE-2026-45413 disclosed?
CVE-2026-45413 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45413 actively exploited?
CVE-2026-45413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45413?
CVE-2026-45413 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-45413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45413, 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-45413

Explore →

Is Your Infrastructure Affected by CVE-2026-45413?

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

Start Free Scan →Browse All CVEs