CVE-2025-64703
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMaxKB 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMaxKB versions prior to 2.3.1 contain a sandbox bypass vulnerability in the tool module where Python code execution can be leveraged to access sensitive information despite running in a sandboxed environment. This is an information disclosure issue with medium severity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine MaxKB installation versionRun the command to retrieve the MaxKB version (e.g., maxkb --version, docker images, or check the About/API endpoint)Affected if The installed version is below 2.3.1
-
Verify tool module is enabledCheck MaxKB configuration or settings for the tool module feature (often via config files, admin UI, or API listing active modules)Affected if The tool module is enabled and operational in the environment
-
Inspect sandbox configurationReview MaxKB sandbox settings in configuration files or admin interface to confirm sandbox enforcement is presentAffected if Sandbox is configured but may be bypassed via the tool module vulnerability
-
Check for unauthorized access indicatorsReview logs for suspicious Python code execution patterns or unexpected file/system access through the tool moduleAffected if Logs show Python execution attempts or access to sensitive files outside expected scope
The environment is affected if MaxKB version is below 2.3.1 and the tool module is enabled, allowing potential sandbox bypass for sensitive information access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.3.1
Upgrade MaxKB to version 2.3.1 or later to remediate the sandbox bypass vulnerability that allows unauthorized sensitive information access.
MaxKB 2.3.1
- 1. Backup your current MaxKB installation and database
- 2. Check the current installed version of MaxKB
- 3. Download MaxKB version 2.3.1 from the official GitHub repository (github.com/1Panel-dev/MaxKB)
- 4. Follow the upgrade instructions provided in the MaxKB documentation for your deployment method (Docker, pip, or source)
- 5. Verify the upgrade was successful by checking the version number
- 6. Test that the sandbox properly restricts Python code execution in tool modules
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64703 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data