Skip to main content
CVE-2025-53928VulnerabilityPublished

CVE-2025-53928: 1Panel-dev MaxKB · Code Injection

Affects 1Panel-dev MaxKBSource CVE Database V5

0

Not known to be exploited · CVSS 4.6 Medium : upgrade to 2.0.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade 1panel-dev/MaxKB to 2.0.0.

Affected software

ProductAffectedFixed in
GitHub1panel-dev/MaxKBpkg:github/1panel-dev/MaxKBOther threatsAffected
  • <2.0.0
  • =1.10.9-lts
Fixed in
  • 2.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to MaxKB versions 1.10.9-lts or 2.0.0, which contain the patches addressing this vulnerability. 2. Implement strict input validation and sanitization on all user inputs and API calls related to the MCP functionality to prevent code injection attempts. 3. Restrict network access to MaxKB management interfaces and MCP endpoints using network segmentation, firewalls, and access control lists to limit exposure to untrusted networks. 4. Employ application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block suspicious command injection patterns. 5. Conduct regular security audits and code reviews focusing on dynamic code generation or execution features within MaxKB or similar AI assistant tools. 6. Educate users on the risks of social engineering and the importance of cautious interaction with prompts or commands that could trigger code execution. 7. Monitor logs and system behavior for unusual command execution or anomalies that could indicate exploitation attempts. 8. If feasible, run MaxKB with the least privileges necessary and isolate it within containerized or sandboxed environments to reduce the blast radius of potential exploitation.

Description

MaxKB is an open-source AI assistant for enterprise. Prior to versions 1.10.9-lts and 2.0.0, a Remote Command Execution vulnerability exists in the MCP call. Versions 1.10.9-lts and 2.0.0 fix the issue.

References

Community reviews

Loading reviews…