{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79746 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-79746 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-79746 is a high-severity missing authorization vulnerability in samanhappy mcphub, published on 31 Aug 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-79746 and fix it if it is affected.\n\nWhat it is: CVE-2026-79746 is a high-severity missing authorization vulnerability in samanhappy mcphub, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-79746 in the wild and no public exploit code.\n\nAffected product: samanhappy mcphub. 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-79746/ (Markdown: https://insights.sbomify.com/CVE-2026-79746/index.md)","id":"CVE-2026-79746","markdown":"https://insights.sbomify.com/CVE-2026-79746/index.md","name":"CVE-2026-79746","record":{"aliases":["GHSA-454m-4vm6-842f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP server hub","requires_auth":"low_privilege","summary":"Attackers with a key scoped to one server can access all servers in the same group due to flawed authorization logic in MCPHub.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"MCPHub is a unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies. Prior to version 1.0.31, when a bearer key with accessType: 'servers' (or 'custom') is used against a group route, isBearerKeyAllowedForRequest grants access to the entire group as long as any single server in that group appears in the key's allowedServers list — not only when every server the key is scoped to matches, and critically, without ever re-checking allowedServers again once the group-level connection is authorized. A key explicitly scoped to one specific server therefore also grants full access to every other server that happens to share a group with it, including servers the key was never authorized for. This issue has been patched in version 1.0.31.","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":"MCPHub: Server-scoped bearer key gains access to an entire group via partial (any-overlap) server matching","id":"CVE-2026-79746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Server-side request forgery in mcphub","id":"CVE-2026-79747"},"packages":[],"prev":{"headline":"Missing authorization in mcphub","id":"CVE-2026-79745"},"products":["mcphub"],"published":"2026-08-31","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["samanhappy"]},"summary":"Attackers with a key scoped to one server can access all servers in the same group due to flawed authorization logic in MCPHub.","url":"https://insights.sbomify.com/CVE-2026-79746/"}