{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-14537 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-14537 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-14537 is a high-severity missing authorization vulnerability in Google mcp-toolbox, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-14537 and fix it if it is affected.\n\nWhat it is: CVE-2026-14537 is a high-severity missing authorization vulnerability in Google mcp-toolbox, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-14537 in the wild and no public exploit code.\n\nAffected product: Google mcp-toolbox. 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-14537/ (Markdown: https://insights.sbomify.com/CVE-2026-14537/index.md)","id":"CVE-2026-14537","markdown":"https://insights.sbomify.com/CVE-2026-14537/index.md","name":"CVE-2026-14537","record":{"aliases":["GHSA-f8h2-c55w-8m5p"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"MCP Toolbox","requires_auth":"none","summary":"Unauthenticated attackers can bypass authorization to invoke protected tools via legacy HTTP endpoints when the API flag is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"mcp_toolbox_for_databases","vendor":"google"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Incorrect Authorization in the direct HTTP API tool invocation endpoint in Google mcp-toolbox versions v1.3.0 and v1.4.0 allows an unauthenticated attacker to invoke tools protected by the scopeRequired feature via sending tool invocation requests through legacy HTTP endpoints when the --enable-api flag is active.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Authorization Bypass in MCP Toolbox Legacy HTTP Endpoints","id":"CVE-2026-14537","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":"BigQuery Dataset Allowlist Bypass via Metadata Dry-Run in MCP Toolbox","id":"CVE-2026-14538"},"packages":[],"prev":{"headline":"Auth bypass in Server","id":"CVE-2026-14536"},"products":["mcp-toolbox"],"published":"2026-07-31","related":[{"cvss_score":9.3,"headline":"Path Traversal in googleapis/mcp-toolbox HTTP Tool URL Builder","id":"CVE-2026-11720","kev_date_added":null,"published":"2026-06-29"},{"cvss_score":9.3,"headline":"googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)","id":"CVE-2026-11717","kev_date_added":null,"published":"2026-06-18"},{"cvss_score":9.3,"headline":"googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)","id":"CVE-2026-11718","kev_date_added":null,"published":"2026-06-18"},{"cvss_score":8.6,"headline":"SQL Injection and Security Boundary Bypass in googleapis/mcp-toolbox","id":"CVE-2026-15829","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.6,"headline":"MCP Toolbox for Databases: authenticated authorization bypass","id":"CVE-2026-11719","kev_date_added":null,"published":"2026-06-18"},{"cvss_score":8,"headline":"Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox","id":"CVE-2026-14540","kev_date_added":null,"published":"2026-07-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-31","vendors":["Google"]},"summary":"Unauthenticated attackers can bypass authorization to invoke protected tools via legacy HTTP endpoints when the API flag is enabled.","url":"https://insights.sbomify.com/CVE-2026-14537/"}