CVE-2025-66446: 1Panel-dev MaxKB · Race Condition
Affects 1Panel-dev MaxKBSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 2.4.0 soon.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade 1panel-dev/MaxKB to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHub1panel-dev/MaxKBpkg:github/1panel-dev/MaxKBOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade all MaxKB deployments to version 2.4.0 or later to apply the official fix addressing file permissions and synchronization issues. 2. Implement strict file system access controls to restrict write permissions on critical system files and directories, especially those related to dynamic linking and executable loading. 3. Employ runtime integrity monitoring tools to detect unauthorized changes to critical files and binaries. 4. Use application whitelisting to prevent execution of unauthorized or modified binaries. 5. Conduct regular audits of user privileges and remove unnecessary elevated permissions to reduce the risk of exploitation by low-privilege attackers. 6. Monitor system and application logs for unusual file access patterns or concurrent execution anomalies indicative of race condition exploitation attempts. 7. Isolate AI assistant environments using containerization or sandboxing to limit the impact of potential compromises. 8. Educate system administrators and security teams about the specific risks associated with race conditions and improper file permissions in AI assistant software.
Description
MaxKB is an open-source AI assistant for enterprise. Versions 2.3.1 and below have improper file permissions which allow attackers to overwrite the built-in dynamic linker and other critical files, potentially resulting in privilege escalation. This issue is fixed in version 2.4.0.