CVE-2026-45413: MaxKB unsalted MD5 password hashing

CVE-2026-45413 · Severity: info · CVSS 6.9 · Published 2026-05-26

MaxKB, an open-source AI assistant for enterprise environments, was found to store user passwords using an obsolete and insecure method. Because passwords were not properly protected with modern encryption techniques, an attacker who gains access to the database could easily recover the original passwords. This could lead to unauthorized access to corporate data and account takeovers across the organization.

Technologies: 1Panel-dev MaxKB. Vendors: 1Panel-dev.

Quick answers

Is CVE-2026-45413 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45413 being exploited in the wild.
How severe is CVE-2026-45413?
Informational severity, with a CVSS score of 6.9, published 26 May 2026.
Which products and versions are affected?
1Panel-dev MaxKB < 2.9.1.
Is there a fix for CVE-2026-45413?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-45413 attacked?
It is attacked from the adjacent network, in a network appliance.
Am I affected by CVE-2026-45413?
Check whether you run 1Panel-dev MaxKB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

MaxKB prior to version 2.9.1 utilizes unsalted MD5 hashes for user password storage, specifically within the password_encrypt function in apps/common/utils/common.py. MD5 is a cryptographically broken hash function, and the lack of a unique salt allows for trivial recovery of plaintext passwords using rainbow tables or GPU-accelerated brute-force attacks (e.g., hashcat). An attacker with read access to the backend database can compromise all user accounts. The vulnerability was addressed in version 2.9.1 by implementing more secure hashing mechanisms.

Affected products

  • 1Panel-dev MaxKB < 2.9.1

Timeline

  • 2026-05-14: advisory: GitHub security advisory published
  • 2026-05-26: disclosed: CVE-2026-45413 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.