CVE-2026-39418: MaxKB: SSRF via sandbox network hook bypass
MaxKB is an open-source AI assistant for enterprise. In versions 2.7.1 and below, sandbox network protection can be bypassed by using socket.sendto() with the MSGFASTOPEN flag. This allows authenticated user with tool-editing permissions to reach internal services that are explicitly blocked by the sandbox's banned hosts configuration. MaxKB's sandbox uses LDPRELOAD to hook the connect() function and block connections to banned IPs, but Linux's sendto() with the MSGFASTOPEN flag can establish TCP connections directly through the kernel without ever calling connect(), completely bypassing the IP validation. Although sendto is listed in the syscall() wrapper, this is ineffective because glibc invokes the kernel syscall directly rather than routing through the hooked syscall() function. This issue has been fixed in version 2.8.0.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39418?
CVE-2026-39418 is considered a high severity vulnerability due to its potential for unauthorized access to internal resources.
How do I fix CVE-2026-39418?
To fix CVE-2026-39418, upgrade MaxKB to version 2.8.0 or later, which addresses the sandbox network hook bypass.
Who is affected by CVE-2026-39418?
All users of MaxKB versions 2.7.1 and below with tool-editing permissions are affected by CVE-2026-39418.
What can happen if CVE-2026-39418 is exploited?
If exploited, CVE-2026-39418 allows an authenticated user to access internal systems, risking data confidentiality.
What is the cause of CVE-2026-39418?
CVE-2026-39418 is caused by a bypass of the sandbox network protection due to the improper handling of the socket.sendto() method with the MSG_FASTOPEN flag.