Quick answers
- Is CVE-2026-42335 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42335 being exploited in the wild.
- How severe is CVE-2026-42335?
- Informational severity, with a CVSS score of 6.3, published 26 May 2026.
- Which products and versions are affected?
- 1Panel-dev MaxKB <= 2.8.0.
- Is there a fix for CVE-2026-42335?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-42335 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42335?
- 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 due to a URL parsing discrepancy. The application uses Python's 'urlparse' for validation but the 'requests' library for the actual HTTP call. An attacker can provide a malformed URL (e.g., using backslashes and @ symbols) that 'urlparse' interprets as a safe external host while 'requests' interprets as an internal IP address. This allows authenticated attackers to bypass security filters and reach internal network services. The issue is resolved in version 2.8.1 by unifying the parsing logic.
Affected products
- 1Panel-dev MaxKB <= 2.8.0
Timeline
- 2026-05-06: advisory: GitHub Security Advisory published
- 2026-05-26: disclosed: CVE published to NVD