Quick answers
- Is CVE-2026-56779 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56779 being exploited in the wild.
- How severe is CVE-2026-56779?
- Medium severity, with a CVSS score of 6.4, published 25 June 2026.
- Which products and versions are affected?
- 1Panel-dev MaxKB < 2.10.0.
- Is there a fix for CVE-2026-56779?
- A patch was published on 2026-06-25: Fix committed in version 2.10.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56779 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-56779?
- 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 prior to 2.10.0 within the ToolSerializer endpoints. The root cause is a failure to validate the 'downloadCallbackUrl' and 'download_url' parameters in the tool creation and update workflows. An authenticated attacker with the default 'USER' role can supply malicious URLs that the server will subsequently request using the Python 'requests' library. This can be used to perform internal port scanning or interact with internal services (like Redis) that are not exposed to the public internet. The vulnerability was addressed in version 2.10.0 by implementing URL validation checks to ensure requests are only made to trusted domains.
Affected products
- 1Panel-dev MaxKB < 2.10.0
Timeline
- 2026-06-01: disclosed: Initial report to vendor via email
- 2026-06-24: other: Public issue opened on GitHub repository
- 2026-06-25: advisory: CVE published and NVD entry created
- 2026-06-25: patched: Fix committed in version 2.10.0