1Panel-dev MaxKB up to 2.7.x ToolExecutor sandbox.so LD_PRELOAD protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 2.52- |
Summary
A vulnerability classified as critical has been found in 1Panel-dev MaxKB up to 2.7.x. This impacts an unknown function of the file sandbox.so of the component ToolExecutor. This manipulation of the argument LD_PRELOAD causes protection mechanism. This vulnerability appears as CVE-2026-39421. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability has been found in 1Panel-dev MaxKB up to 2.7.x and classified as critical. Affected by this vulnerability is some unknown processing of the file sandbox.so of the component ToolExecutor. The manipulation of the argument LD_PRELOAD with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
MaxKB is an open-source AI assistant for enterprise. Versions 2.7.1 and below contain a sandbox escape vulnerability in the ToolExecutor component. By leveraging Python's ctypes library to execute raw system calls, an authenticated attacker with workspace privileges can bypass the LD_PRELOAD-based sandbox.so module to achieve arbitrary code execution via direct kernel system calls, enabling full network exfiltration and container compromise. The library intercepts critical standard system functions such as execve, system, connect, and open. It also intercepts mprotect to prevent PROT_EXEC (executable memory) allocations within the sandboxed Python processes, but pkey_mprotect is not blocked. This issue has been fixed in version 2.8.0.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-39421 since 04/07/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2.8.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 479701a4d2e6059506bad0057a66bed91abb5aef is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/1Panel-dev/MaxKB/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.3
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Protection mechanismCWE: CWE-693
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: MaxKB 2.8.0
Patch: 479701a4d2e6059506bad0057a66bed91abb5aef
Timeline
04/07/2026 CVE reserved04/14/2026 Advisory disclosed
04/14/2026 VulDB entry created
04/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-9c6w-j7w5-3gf7
Status: Confirmed
CVE: CVE-2026-39421 (🔒)
GCVE (CVE): GCVE-0-2026-39421
GCVE (VulDB): GCVE-100-357223
Entry
Created: 04/14/2026 07:35Changes: 04/14/2026 07:35 (69)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.