# CVE-2026-64870: MaxKB: UpdateStoreTool fetches caller-supplied app-store URLs without host validation

> Authenticated users can force the MaxKB server to request internal or cloud metadata URLs via unvalidated store update tools.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-7xxm-gqxv-ph3v

## What is CVE-2026-64870?

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

### Official description

MaxKB is an open-source AI assistant for enterprise. In versions 2.0.0 through 2.10.4-lts, UpdateStoreTool.update_tool passes caller-supplied download_url and download_callback_url values to requests.get without equivalent trusted-host and redirect validation, allowing an authenticated workspace user to make the server request internal, loopback, link-local, or cloud metadata URLs. A fix is present on the v2 branch but has not yet been included in a published release.

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

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


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

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

## Is CVE-2026-64870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64870 is a medium-severity server-side request forgery vulnerability in 1Panel-dev MaxKB, published on 30 Jul 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-64870 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-64870/ (Markdown: https://insights.sbomify.com/CVE-2026-64870/index.md)
```

## Sources

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

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