# CVE-2026-77522: Server-side request forgery in MaxKB

> Authenticated users can exploit the web-document crawler to read internal network resources and cloud metadata via Server-Side Request Forgery.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 21 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-ffxw-frpx-8rww

## What is CVE-2026-77522?

CVE-2026-77522 is a medium-severity server-side request forgery vulnerability in 1Panel-dev MaxKB, published on 21 Sep 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 version 2.10.3-lts and earlier, the knowledge web-document import and synchronization crawler passes an authenticated workspace user's URL to Fork.fork, which calls requests.get with verify=False and without restricting schemes, loopback, link-local, private, or reserved addresses. The response body is converted into imported document content, allowing a low-privileged user to read cloud metadata or internal HTTP services through the MaxKB server. No fixed version is available as of this review.

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

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


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

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

## Is CVE-2026-77522 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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