Quick answers
- Is CVE-2026-42336 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42336 being exploited in the wild.
- How severe is CVE-2026-42336?
- Informational severity, with a CVSS score of 5.1, published 26 May 2026.
- Which products and versions are affected?
- 1Panel-dev MaxKB <= 2.8.0.
- Is there a fix for CVE-2026-42336?
- A patch was published on 2026-05-26: Fix confirmed available in version 2.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42336 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42336?
- Check whether you run 1Panel-dev MaxKB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the /chat/api/oss/get_url endpoint of MaxKB due to a Time-of-Check Time-of-Use (TOCTOU) flaw in DNS resolution. The application performs an initial DNS lookup to validate that a target host is not a private IP address, but then performs a second, independent DNS resolution when executing the actual HTTP request via the 'requests' library. This inconsistency allows for a DNS rebinding attack where an attacker can provide a domain that resolves to a public IP during validation but a private IP during execution. An authenticated attacker can exploit this to bypass internal network restrictions. The vulnerability is fixed in version 2.8.1 by resolving and locking the IP address before the request and validating the connected peer IP.
Affected products
- 1Panel-dev MaxKB <= 2.8.0
Timeline
- 2026-05-07: advisory: GitHub Security Advisory published
- 2026-05-26: disclosed: CVE published to NVD
- 2026-05-26: patched: Fix confirmed available in version 2.8.1