# CVE-2025-64703: MaxKB has Information Leak in sandbox

> Attackers can leak sensitive information via Python code in the tool module despite sandboxing, affecting enterprise AI assistant deployments.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 13 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-qwvm-x4xh-g2qq

## What is CVE-2025-64703?

CVE-2025-64703 is a medium-severity vulnerability in 1Panel-dev MaxKB, published on 13 Nov 2025. 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 prior to 2.3.1, a user can get sensitive informations by Python code in tool module, although the process run in sandbox. Version 2.3.1 fixes the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-64703?

It affects 1 product.


Products: Maxkb Maxkb.

## How do I fix CVE-2025-64703?

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

## Is CVE-2025-64703 being exploited?

There is no known exploitation of CVE-2025-64703 in the wild and no public exploit code.

## Other vulnerabilities in 1Panel-dev MaxKB

- [CVE-2025-66419](https://insights.sbomify.com/CVE-2025-66419/): MaxKB vulnerable to privilege escalation through sandbox bypass (high 8.8)
- [CVE-2025-66446](https://insights.sbomify.com/CVE-2025-66446/): MaxKB has a Python sandbox LD_PRELOAD bypass (high 8.8)
- [CVE-2025-64511](https://insights.sbomify.com/CVE-2025-64511/): MaxKB has SSRF in sandbox (high 7.4)
- [CVE-2026-39422](https://insights.sbomify.com/CVE-2026-39422/): MaxKB has Stored XSS via ChatHeadersMiddleware (medium 6.9)
- [CVE-2026-39423](https://insights.sbomify.com/CVE-2026-39423/): Stored XSS via Eval Injection in EchartsRander Component (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64703 and fix it if it is affected.

What it is: CVE-2025-64703 is a medium-severity vulnerability in 1Panel-dev MaxKB, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64703 in the wild and no public exploit code.

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-2025-64703/ (Markdown: https://insights.sbomify.com/CVE-2025-64703/index.md)
```

## Sources

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

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