Skip to main content
VulnerabilityPublished

CVE-2026-39418: 1Panel-dev MaxKB · Server-Side Request Forgery (SSRF)

Affects 1Panel-dev MaxKBSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 2.8.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Upgrade MaxKB and 1panel-dev/MaxKB to 2.8.0.

Affected software

ProductAffectedFixed in
1Panel-devMaxKBAffected
  • <2.8.0
Fixed in
  • 2.8.0
GitHub1panel-dev/MaxKBpkg:github/1panel-dev/MaxKBOther threatsAffected
  • <2.8.0
Fixed in
  • 2.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability has been fixed in MaxKB version 2.8.0. Users should upgrade to version 2.8.0 or later to remediate this issue. Since the product is not a cloud service, remediation requires applying the official patch by updating the software. No other vendor advisory or temporary fixes are provided. Patch status is confirmed by the vendor's versioning information.

Description

CVE-2026-39418 is a Server-Side Request Forgery (SSRF) vulnerability in MaxKB versions 2.7.1 and below. The issue arises because the sandbox network protection can be bypassed using the socket.sendto() function with the MSG_FASTOPEN flag, allowing authenticated users with tool-editing permissions to access internal services blocked by the sandbox. This bypass occurs because the sandbox hooks the connect() function to block banned IPs, but sendto() with MSG_FASTOPEN establishes TCP connections without calling connect(), circumventing IP validation. The vulnerability has been fixed in MaxKB version 2.8.0. The CVSS score is 5.

References

Community reviews

Loading reviews…