dbcve.org
MaxkbApplication

CVE-2025-53928

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-17
Fix available
A fix is available. Upgrade to 1.10.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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. Prior to versions 1.10.9-lts and 2.0.0, a Remote Command Execution vulnerability exists in the MCP call. Versions 1.10.9-lts and 2.0.0 fix 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 · high confidence

MaxKB (an open-source AI assistant for enterprise) versions prior to 1.10.9-lts and 2.0.0 contain a Remote Command Execution vulnerability in the MCP call functionality. The vulnerability is exploitable remotely without authentication (CVSS 9.8), allowing attackers to execute arbitrary commands on the host system through the vulnerable MCP interface.

MitigationUpgrade MaxKB to version 1.10.9-lts or 2.0.0 to remediate this vulnerability. As this is a critical RCE, immediate patching is recommended; no compensating controls are specified in the advisory.

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:< 1.10.9

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 if MaxKB is running
    Check for MaxKB processes or services running on the system. Look for process names like 'maxkb' or check if port 8080 (default MaxKB port) is in use.
    Affected if MaxKB service is found running on the system
  2. Determine installed MaxKB version
    Check the installed MaxKB version using the package manager, container image tag, or application UI. Compare the version number against the affected range (versions prior to 1.10.9).
    Affected if Installed version is less than 1.10.9-lts or 2.0.0
  3. Verify MCP functionality is enabled
    Inspect MaxKB configuration files or settings to determine if the Model Context Protocol (MCP) call feature is enabled or configured.
    Affected if MCP call functionality is enabled and accessible (the vulnerability exists in this component)
  4. Check for unauthorized command execution
    Review MaxKB service logs for suspicious command execution entries, unexpected shell commands, or unusual API calls to the MCP endpoint.
    Affected if Evidence of arbitrary commands executed through the MCP interface that were not initiated by authorized administrators

You are affected if MaxKB is running with a version prior to 1.10.9-lts or 2.0.0 and the MCP call functionality is enabled and exposed.

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 1.10.9 or later
Fixed in 1.10.9
Interim mitigation

Upgrade MaxKB to version 1.10.9-lts or 2.0.0 to remediate this vulnerability. As this is a critical RCE, immediate patching is recommended; no compensating controls are specified in the advisory.

Recommended fix High confidence

1.10.9-lts or 2.0.0

  1. 1. Backup your current MaxKB installation and database before upgrading.
  2. 2. Identify your current MaxKB version by checking the application or using the version command.
  3. 3. Stop the MaxKB service to prevent any during-upgrade conflicts.
  4. 4. Upgrade MaxKB to version 1.10.9-lts (recommended for stability) or 2.0.0 (latest major version). Follow the standard upgrade procedure for your deployment method (Docker, pip, or source).
  5. 5. Start the MaxKB service after the upgrade completes.
  6. 6. Verify the version has been updated to 1.10.9-lts or 2.0.0.
  7. 7. Test that the MCP functionality works correctly after the upgrade.
Caveat Upgrade to 2.0.0 may introduce breaking changes; 1.10.9-lts is the recommended stable LTS path

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

Fix this in Maxkb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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