dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-6108

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability was found in 1Panel-dev MaxKB up to 2.6.1. The affected element is the function execute of the file apps/application/flow/step_node/mcp_node/impl/base_mcp_node.py of the component Model Context Protocol Node. Performing a manipulation results in os command injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used. You should upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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

OS command injection vulnerability in the Model Context Protocol Node's execute function within MaxKB (1Panel-dev) up to version 2.6.1. The vulnerability exists in base_mcp_node.py and allows remote attackers to inject and execute arbitrary OS commands through the affected function.

MitigationUpgrade MaxKB to the fixed version released by the vendor (version higher than 2.6.1) to remediate this command injection vulnerability.

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
Low
Integrity
Low
Availability
Low

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

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 and version
    Locate the MaxKB application and retrieve its version number. Common methods: check the application's about page, look for a version file in the installation directory, or run 'maxkb --version' if CLI is available.
    Affected if The installed version is 2.6.1 or lower (any version up to and including 2.6.1)
  2. Locate the vulnerable base_mcp_node.py file
    Search for the file named 'base_mcp_node.py' within the MaxKB installation directory. Common paths include: <maxkb_install_dir>/base_mcp_node.py or under a 'nodes' or 'mcp' subdirectory.
    Affected if The file exists in the MaxKB installation, indicating the MCP Node component is present
  3. Verify the execute function exists in base_mcp_node.py
    Open base_mcp_node.py and locate the 'execute' function definition within it. Inspect whether the function processes user-supplied input and passes it to system command execution methods (e.g., os.system, subprocess calls, shell=True).
    Affected if The execute function is present and contains code that executes OS commands using unsanitized input
  4. Check if MCP feature is enabled or configured
    Review MaxKB configuration files (such as config.py, settings.py, or any .env file) for MCP-related settings. Look for flags like 'MCP_ENABLED', 'enable_mcp', or configurations referencing 'model_context_protocol'.
    Affected if MCP feature is enabled in the configuration, making the vulnerable code path reachable
  5. Review MCP node usage in applications
    Check if any MaxKB applications or workflows are using the Model Context Protocol Node. Look at application definitions, workflow configurations, or database records that reference MCP nodes.
    Affected if Any application or workflow actively uses the MCP Node component

You are affected if MaxKB version is 2.6.1 or lower AND the base_mcp_node.py file exists AND the MCP feature or node is enabled/used in your environment.

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 MaxKB to the fixed version released by the vendor (version higher than 2.6.1) to remediate this command injection vulnerability.

Recommended fix Moderate confidence

MaxKB version 2.6.2 or later

  1. 1. Back up your current MaxKB installation and database before performing any upgrade.
  2. 2. Check the official 1Panel-dev MaxKB repository or release page for the latest available version.
  3. 3. Download and install the fixed version (version 2.6.2 or later, as the vulnerability affects versions up to 2.6.1).
  4. 4. Verify the upgrade was successful by checking the installed version.
  5. 5. Test the Model Context Protocol Node functionality to confirm the command injection vulnerability is remediated.
  6. 6. Review application logs for any suspicious activity that may indicate exploitation attempts.
Caveat Review release notes for any breaking changes between 2.6.1 and the target version before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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