dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-54149

HIGH · 8.8 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 weeks old

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 2.10.0-lts, MaxKB tool import functionality in apps/tools/serializers/tool.py and MCP referencing mode in apps/application/chat_pipeline/step/chat_step/impl/base_chat_step.py do not consistently validate MCP transport type, allowing an authenticated user to import a .tool file containing stdio transport with malicious commands and trigger the configuration through an AI Chat node so MultiServerMCPClient executes arbitrary system commands. This issue is fixed in version 2.10.0-lts.

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 tool import and MCP referencing modes fail to validate MCP transport types, allowing authenticated users to import .tool files with malicious stdio transport commands that get executed by MultiServerMCPClient when triggered via AI Chat nodes.

MitigationUpgrade to MaxKB 2.10.0-lts or apply the patch to validate MCP transport types in apps/tools/serializers/tool.py and apps/application/chat_pipeline/step/chat_step/impl/base_chat_step.py to prevent arbitrary command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Check MaxKB version
    Run 'maxkb --version' or check the application UI for the version number, or inspect the package manager if installed via pip
    Affected if Version is earlier than 2.10.0-lts (the fix version)
  2. Identify tool import activity
    Search for .tool files in the application data directory, or check the tools configuration for imported custom tools
    Affected if Custom .tool files have been imported into the system
  3. Examine tool serializer code
    Inspect apps/tools/serializers/tool.py for lack of MCP transport type validation - look for absence of validation logic that checks transport type before accepting stdio or other transports
    Affected if The code lacks validation that rejects untrusted transport types in imported tools
  4. Examine chat step code
    Inspect apps/application/chat_pipeline/step/chat_step/impl/base_chat_step.py for missing transport validation before passing to MultiServerMCPClient
    Affected if The code directly passes transport configuration without validating it comes from a trusted source
  5. Check MCP client usage
    Search codebase for MultiServerMCPClient instantiation and trace how transport parameters from tool definitions are passed to it
    Affected if Transport type from imported .tool files flows directly to MultiServerMCPClient without sanitization

You are affected if running MaxKB version earlier than 2.10.0-lts and custom .tool files have been imported or MCP references use unvalidated transport configurations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to MaxKB 2.10.0-lts or apply the patch to validate MCP transport types in apps/tools/serializers/tool.py and apps/application/chat_pipeline/step/chat_step/impl/base_chat_step.py to prevent arbitrary command execution.

Recommended fix High confidence

2.10.0-lts

  1. 1. Backup your current MaxKB installation and database before upgrading.
  2. 2. Stop the running MaxKB service.
  3. 3. If using Docker, pull the new image with tag 2.10.0-lts: docker pull 1panel/maxkb:v2.10.0-lts
  4. 4. If using installation scripts or package managers, upgrade to version 2.10.0-lts following your deployment method.
  5. 5. Verify the upgrade completed successfully by checking the version number in the admin interface or via CLI.
  6. 6. Start the MaxKB service.
  7. 7. As a best practice after upgrade, review user permissions and audit logs to ensure no malicious tools were imported prior to patching.
Caveat Review release notes for 2.10.0-lts for any configuration or migration changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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