# CVE-2026-56779: MaxKB < 2.10.0 - Server-Side Request Forgery via downloadCallbackUrl and download_url Parameters

> Authenticated users can exploit unvalidated URL parameters in MaxKB to perform server-side request forgery and access internal network services.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-395g-c5fv-7hfh

## What is CVE-2026-56779?

CVE-2026-56779 is a medium-severity server-side request forgery vulnerability in 1Panel-dev MaxKB, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MaxKB before 2.10.0 contains a server-side request forgery vulnerability in tool creation and update endpoints that allows authenticated users to make arbitrary server requests by supplying unvalidated downloadCallbackUrl and download_url parameters. Attackers with default workspace USER role can exploit this to access internal network services by providing malicious URLs to the ToolSerializer endpoints.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-56779?


## How do I fix CVE-2026-56779?

No fix has been published for CVE-2026-56779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56779 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56779 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56779 and fix it if it is affected.

What it is: CVE-2026-56779 is a medium-severity server-side request forgery vulnerability in 1Panel-dev MaxKB, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56779 exists.

Affected product: 1Panel-dev MaxKB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56779/ (Markdown: https://insights.sbomify.com/CVE-2026-56779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56779
- OSV: https://osv.dev/vulnerability/CVE-2026-56779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56779/
Summaries are generated and may contain mistakes; the official description above is the record.