CVE-2026-79919: 1Panel-dev MaxKB · Protection Mechanism Failure
Affects 1Panel-dev MaxKBSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.10.6-lts when convenient.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.10.6-lts
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 2026.
What to do
Upgrade MaxKB and 1panel-dev/MaxKB to 2.10.6-lts.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| 1Panel-devMaxKB | 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
Upgrade MaxKB to version 2.10.6-lts or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-79919 is a protection mechanism failure vulnerability in MaxKB, an open-source AI assistant for enterprise. Versions prior to 2.10.6-lts allow an authenticated workspace member to bypass the LD_PRELOAD sandbox syscall blacklist by exploiting a flaw in how ctypes.CDLL is invoked from a MetaPathFinder callback. This enables unauthorized read/write file access, process execution, and network access as the sandbox user. The issue is fixed in version 2.10.6-lts.