CVE-2026-77516

MaxKB: Missing per-tool authorization in the agent and workflow tool-dispatch path

Published Sep 21, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
MaxKB is an open-source AI assistant for enterprise. From version 2.0.0 through 2.9.2, a lowest-role workspace member denied access to a tool by WorkspaceUserResourcePermission can still bind its identifier through tool_ids, skill_tool_ids, or mcp_tool_ids and execute it through the agent or workflow dispatch path. The dispatch path does not reapply the per-tool grant enforced by dedicated tool routes, and tool execution decrypts server-side init_params, allowing the caller to receive credentials carried by the denied tool. No fixed version is available as of this review.

Analysis

AI-generated

Technical impact

MaxKB allows a lowest–role workspace member to bind a tool it was denied access to through tool_ids, skill_tool_ids, or mcp_tool_ids and execute it via the agent or workflow dispatch path. The dispatch path does not reapply per–tool grants, so the user can execute the tool and decrypt server–side init_params, exposing credentials carried by the denied tool. The flaw is a privilege‑escalation vulnerability that can leak sensitive credential information.

Affected Systems

1Panel‑dev MaxKB versions 2.0.0 through 2.9.2 are affected. No fixed version is available at the time of this review.

Risk and Exploitability

The CVSS score of 5.4 indicates moderate severity. EPSS data is not available and the vulnerability is not listed in CISA KEV. The attack vector is likely through the agent or workflow dispatch API, and it requires a legitimate workspace membership at the lowest role. Once exploited, the attacker can read decrypted init_params and obtain credentials, potentially compromising other services controlled by those credentials.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Restrict low‑privilege workspace members from binding or executing tools that they are not authorized for.
  • Disable or limit access to the agent and workflow dispatch paths for users with lowest role.
  • Monitor system logs for unauthorized tool executions and investigate anomalies.

Generated by OpenCVE AI on September 21, 2026 at 22:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared 1panel
1panel maxkb
Vendors & Products 1panel
1panel maxkb
Type Values Removed Values Added
Description MaxKB is an open-source AI assistant for enterprise. From version 2.0.0 through 2.9.2, a lowest-role workspace member denied access to a tool by WorkspaceUserResourcePermission can still bind its identifier through tool_ids, skill_tool_ids, or mcp_tool_ids and execute it through the agent or workflow dispatch path. The dispatch path does not reapply the per-tool grant enforced by dedicated tool routes, and tool execution decrypts server-side init_params, allowing the caller to receive credentials carried by the denied tool. No fixed version is available as of this review.
Title MaxKB: Missing per-tool authorization in the agent and workflow tool-dispatch path
Weaknesses CWE-639
CWE-862
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 28, 2026, 8:13 PM
Reserved
Aug 20, 2026, 8:23 PM
Status
Deferred
Published
Sep 21, 2026, 9:17 PM
Modified
Sep 28, 2026, 9:17 PM