Skip to main content
CVE-2025-66419VulnerabilityPublished Updated

CVE-2025-66419: 1Panel-dev MaxKB · Race Condition

Affects 1Panel-dev MaxKBSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 2.4.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Dec 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.4.0.

Affected software

ProductAffectedFixed in
GitHub1panel-dev/MaxKBpkg:github/1panel-dev/MaxKBOther threatsAffected
  • <2.4.0
Fixed in
  • 2.4.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 version 2.4.0 or later to apply the official patch fixing the race condition. 2. Conduct a thorough audit of all systems running vulnerable MaxKB versions to identify and isolate affected instances. 3. Implement strict network segmentation and access controls to limit exposure of MaxKB services to trusted internal networks only. 4. Monitor logs and system behavior for unusual concurrent execution patterns or privilege escalation attempts. 5. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) tools capable of detecting race condition exploitation techniques. 6. Review and harden sandbox configurations and concurrency controls within MaxKB deployments. 7. Educate development and operations teams on secure concurrent programming practices to prevent similar issues in custom integrations or extensions. 8. Prepare incident response plans specifically addressing potential AI assistant compromise scenarios.

Description

MaxKB is an open-source AI assistant for enterprise. In versions 2.3.1 and below, the tool module allows an attacker to escape the sandbox environment and escalate privileges under certain concurrent conditions. This issue is fixed in version 2.4.0.

References

Community reviews

Loading reviews…