{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77518 exists.","fix":"No fix has been published for CVE-2026-77518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77518 is a medium-severity missing authorization vulnerability in 1Panel-dev MaxKB, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77518 and fix it if it is affected.\n\nWhat it is: CVE-2026-77518 is a medium-severity missing authorization vulnerability in 1Panel-dev MaxKB, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77518 exists.\n\nAffected product: 1Panel-dev MaxKB. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77518/ (Markdown: https://insights.sbomify.com/CVE-2026-77518/index.md)","id":"CVE-2026-77518","markdown":"https://insights.sbomify.com/CVE-2026-77518/index.md","name":"CVE-2026-77518","record":{"aliases":["GHSA-x65c-w438-c58f"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI assistant platform","requires_auth":"low_privilege","summary":"Attackers can access hidden MCP tool configurations and execute workflows using unauthorized tools due to missing authorization checks in MaxKB.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"MaxKB is an open-source AI assistant for enterprise. In 2.10.2-lts and earlier, a normal workspace user who knows another user's active MCP tool_id in the same workspace can retrieve the hidden tool through the tool-detail route because it does not apply the per-resource authorization used by the list route. The response includes Tool.code, which may contain MCP server configuration and headers, and an attacker who can create or edit an attacker-owned workflow can place the same foreign mcp_tool_id in a workflow mcp-node so workflow debug uses the owner's MCP configuration without verifying permission to use that tool. No fixed version is available as of this review.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"MaxKB: Known MCP tool IDs expose owner Tool.code and can be referenced by attacker workflows","id":"CVE-2026-77518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MaxKB: Expired application API keys remain usable on `/chat/api/mcp`","id":"CVE-2026-77519"},"packages":[],"prev":{"headline":"MaxKB cross-knowledge IDOR lets a normal user read and modify documents and paragraphs in another knowledge base","id":"CVE-2026-77517"},"products":["MaxKB"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["1Panel-dev"]},"summary":"Attackers can access hidden MCP tool configurations and execute workflows using unauthorized tools due to missing authorization checks in MaxKB.","url":"https://insights.sbomify.com/CVE-2026-77518/"}