dbcve.org
MaxkbApplication

CVE-2025-64511

HIGH · 8.8 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 2.3.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
MaxKB is an open-source AI assistant for enterprise. In versions prior to 2.3.1, a user can access internal network services such as databases through Python code in the tool module, although the process runs in a 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 confidence

MaxKB versions prior to 2.3.1 contain a sandbox bypass vulnerability in the tool module that allows authenticated users to execute Python code and access internal network services such as databases. The built-in sandbox provides insufficient isolation, enabling attackers to reach internal infrastructure that should be protected.

MitigationUpgrade to MaxKB version 2.3.1 or later, which implements proper sandboxing to block access to internal network services from the tool module.

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
MaxkbApplication
Affected:< 2.3.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MaxKB installation version
    Run the command to display the installed MaxKB version (for example: maxkb --version, check the Docker image tag, or query the application API for version information)
    Affected if The installed version is lower than 2.3.1 (e.g., 2.3.0, 2.2.x, or earlier)
  2. Verify tool module is accessible
    Check whether the tool module feature is enabled and accessible to authenticated users in the MaxKB configuration or admin panel
    Affected if The tool module is enabled and allows authenticated users to execute custom code or access tool integrations
  3. Inspect sandbox isolation for tool module
    Review the sandbox configuration for the tool module to determine whether internal network services (such as databases or internal APIs) are accessible from within the tool execution environment
    Affected if The sandbox permits outbound network connections to internal services or allows import of sensitive modules that bypass isolation boundaries
  4. Test for internal network access from tool execution
    If the tool module is available, attempt to execute a simple test (such as attempting a network call to an internal-only hostname or service) through the tool execution interface to confirm whether the sandbox permits access to internal infrastructure
    Affected if The tool execution can reach internal network resources that should be blocked by the sandbox

A user is affected if they are running MaxKB version prior to 2.3.1 with the tool module enabled, where the built-in sandbox fails to block access to internal network services from authenticated tool module users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3.1 or later
Fixed in 2.3.1
Interim mitigation

Upgrade to MaxKB version 2.3.1 or later, which implements proper sandboxing to block access to internal network services from the tool module.

Recommended fix Moderate confidence

2.3.1

  1. Upgrade MaxKB to version 2.3.1 or later
  2. If using Docker, pull the latest image with the tag corresponding to version 2.3.1
  3. If using a Python package manager, upgrade the package to the latest release that includes the fix
  4. Restart the MaxKB service after upgrading
  5. Verify the upgrade was successful by checking the application version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maxkb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64511 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64511 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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