Description
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.
Published: 2026-05-26
Score: 6.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

MaxKB, an open‑source AI assistant, stores user passwords using basic MD5 hashes without a salt in releases prior to 2.9.1. MD5 is a fast, one‑way hash algorithm that is now considered weak; without a salt, the hashes can be reversed with rainbow tables or GPU‑accelerated brute‑force tools such as hashcat in a matter of minutes. An attacker who obtains the password database can quickly recover all user credentials, enabling full access to the system, impersonation of privileged users, or further lateral movement. The vulnerability directly exposes stored credentials and compromises confidentiality of user data.

Affected Systems

The vulnerability affects the 1Panel-dev MaxKB product in all versions released before 2.9.1. No specific patch level is listed, but the security advisory states that any deployment of MaxKB older than version 2.9.1 is susceptible. The affected product is a web‑based enterprise AI assistant, and the issue concerns the internal credential storage mechanism used by the application.

Risk and Exploitability

The CVSS score is 6.9, indicating a moderate severity with reasonable impact potential. The EPSS score is not reported, and the vulnerability is not listed in the CISA KEV catalog. The attack path requires an adversary to acquire the password database, which may be achieved through successful exploitation of other vulnerabilities, privileged access, or a breach of database credentials. Once the database is compromised, password cracking is trivial, enabling credential theft and potential escalation to full system compromise. The likelihood of exploitation remains uncertain without EPSS data, but the existence of a fast hash function and the widespread use of unsalted MD5 make the vulnerability valuable to attackers.

Generated by OpenCVE AI on May 26, 2026 at 21:50 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade MaxKB to version 2.9.1 or higher to enable salted, secure password hashing.
  • If an upgrade is not immediately possible, enforce a forced password reset for all users and reconfigure the authentication module to use a strong hashing algorithm such as bcrypt or Argon2.
  • Restrict database access to a least‑privilege set of users, monitor access logs for unusual query patterns, and audit regular credentials backups to detect tampering.

Generated by OpenCVE AI on May 26, 2026 at 21:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 26 May 2026 20:30:00 +0000

Type Values Removed Values Added
Description 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.
Title MaxKB: Unsalted MD5 Password Hashing
Weaknesses CWE-328
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-05-26T20:12:34.805Z

Reserved: 2026-05-12T01:48:40.452Z

Link: CVE-2026-45413

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-26T21:16:40.233

Modified: 2026-05-26T21:16:40.233

Link: CVE-2026-45413

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-26T22:00:15Z

Weaknesses