dbcve.org
MaxkbApplication

CVE-2025-66419

CRITICAL · 10.0 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 2.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 2.3.1 and below, the tool module allows an attacker to escape the sandbox environment and escalate privileges under certain concurrent conditions. This issue is fixed in version 2.4.0.

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 2.3.1 and below contain a sandbox escape vulnerability in the tool module that allows attackers to break out of the isolated environment and escalate privileges. The vulnerability is triggered under specific concurrent conditions, suggesting a race condition or timing-based flaw in how the tool module enforces sandboxing boundaries.

MitigationUpgrade MaxKB to version 2.4.0 or later to remediate this vulnerability. Until upgrade, minimize exposure by restricting access to untrusted users and monitoring for anomalous tool execution patterns.

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.4.0

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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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
    Locate the MaxKB application installation directory or check system packages for maxkb. Common locations include /opt/maxkb, /usr/local/maxkb, or check via package manager (pip show maxkb, docker ps for maxkb containers).
    Affected if MaxKB is installed and the version cannot be determined or is below 2.4.0
  2. Determine installed MaxKB version
    Run the version check command for your installation method: if using pip, run 'pip show maxkb' or 'pip list | grep -i maxkb'; if using docker, run 'docker exec <container> maxkb --version' or check image tag; check /opt/maxkb/VERSION or similar version file if it exists.
    Affected if The installed version is 2.3.1 or below, or any version prior to 2.4.0
  3. Verify tool module is enabled
    Examine MaxKB configuration files (commonly in /etc/maxkb/, /opt/maxkb/config/, or within the application data directory) for tool module settings. Look for entries like 'enable_tool', 'tool_module', or 'tools' in config.yaml, settings.py, or similar configuration files.
    Affected if The tool module is enabled in the MaxKB configuration
  4. Check sandbox configuration for tool execution
    Inspect the sandbox or security configuration files within the MaxKB tool module directory. Look for sandbox-related settings such as 'sandbox_mode', 'isolation_level', or 'exec_permissions' that control the isolated execution environment.
    Affected if Sandbox settings allow broad execution or are set to a permissive mode for tool operations
  5. Review concurrent tool execution patterns
    If available, check MaxKB logs (typically in /var/log/maxkb/ or within the application data logs directory) for concurrent tool execution events. Look for patterns involving rapid successive tool calls that could trigger race conditions in the sandbox.
    Affected if Logs show concurrent tool execution activity and the installed version is below 2.4.0

You are affected if MaxKB is installed with a version below 2.4.0 and the tool module is enabled with sandbox configurations that permit the isolated environment to be bypassed under concurrent conditions.

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.4.0 or later
Fixed in 2.4.0
Vendor patch github.com →
Interim mitigation

Upgrade MaxKB to version 2.4.0 or later to remediate this vulnerability. Until upgrade, minimize exposure by restricting access to untrusted users and monitoring for anomalous tool execution patterns.

Recommended fix High confidence

2.4.0

  1. Identify the current MaxKB installation method (e.g., Docker, pip, or source)
  2. Backup the existing MaxKB data and configuration
  3. Stop the running MaxKB service
  4. Upgrade MaxKB to version 2.4.0 using the appropriate method for your installation
  5. Verify the upgrade was successful by checking the version number
  6. Restart the MaxKB service
Caveat Security fix upgrade; review release notes for any minor behavioral changes

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

Fix this in Maxkb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66419 — 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-66419 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