Quick answers
- Is CVE-2026-64870 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64870 being exploited in the wild.
- How severe is CVE-2026-64870?
- Informational severity, with a CVSS score of 5.3, published 30 July 2026.
- Which products and versions are affected?
- 1Panel-dev MaxKB 2.0.0 - 2.10.4-lts.
- Is there a fix for CVE-2026-64870?
- A patch was published on 2026-07-28: Fix committed to the v2 branch repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64870 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-64870?
- 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 MaxKB versions 2.0.0 through 2.10.4-lts within the `UpdateStoreTool.update_tool` function. The application fails to validate the `download_url` and `download_callback_url` parameters before passing them to the `requests.get` method. An authenticated workspace user can provide malicious URLs pointing to loopback addresses, internal network services, or cloud metadata endpoints (e.g., 169.254.169.254). While the application enforces host-locking in other components, this specific path lacks equivalent trusted-host or redirect validation. A fix involving centralized URL validation has been committed to the v2 branch but may not be in all published releases.
Affected products
- 1Panel-dev MaxKB 2.0.0 - 2.10.4-lts
Timeline
- 2026-07-27: disclosed: Initial advisory publication on GitHub
- 2026-07-28: patched: Fix committed to the v2 branch repository
- 2026-07-30: advisory: CVE-2026-64870 published to NVD