{"answers":{"affected":"3 open source packages ship an affected version, including github.com/modelcontextprotocol/registry. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44428 in the wild and no public exploit code.","fix":"Upgrade github.com/modelcontextprotocol/registry to 1.7.6 or later.","what":"CVE-2026-44428 is a low-severity authentication bypass vulnerability in modelcontextprotocol registry, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44428 and fix it if it is affected.\n\nWhat it is: CVE-2026-44428 is a low-severity authentication bypass vulnerability in modelcontextprotocol registry, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44428 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/modelcontextprotocol/registry (Go): affected all versions; fixed in 1.7.6\n- github.com/modelcontextprotocol/registry (Go): affected all versions; fixed in 1.7.6\n- github.com/modelcontextprotocol/registry (Go): affected all versions; fixed in 1.7.6\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-44428/ (Markdown: https://insights.sbomify.com/CVE-2026-44428/index.md)","id":"CVE-2026-44428","markdown":"https://insights.sbomify.com/CVE-2026-44428/index.md","name":"CVE-2026-44428","record":{"aliases":["GHSA-95c3-6vvw-4mrq","GO-2026-5273"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP Registry","requires_auth":"none","summary":"Attackers can replay GitHub OIDC tokens across different MCP Registry deployments to gain unauthorized publish permissions due to shared audience validation.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mcp_registry","vendor":"lfprojects"}],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.6, the client-side and server-side GitHub OIDC flow is bound only to a global audience string, not to the specific registry instance being targeted. On the client side, the publisher always appends audience=mcp-registry when requesting the GitHub Actions ID token, regardless of the selected --registry URL. On the server side, the exchange endpoint validates only that same fixed audience and then derives publish permissions directly from repository_owner. As a result, a token legitimately obtained while interacting with one registry deployment remains acceptable to any other deployment that shares the same code and audience string. This vulnerability is fixed in 1.7.6.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MCP Registry: GitHub OIDC tokens replayable across registry deployments due to shared audience","id":"CVE-2026-44428","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"MCP Registry: Stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`","id":"CVE-2026-44429"},"packages":[{"ecosystem":"Go","fixed":["1.7.6"],"introduced":["0"],"last_affected":[],"package":"github.com/modelcontextprotocol/registry","purl":null,"source":"GHSA-95c3-6vvw-4mrq"},{"ecosystem":"Go","fixed":["1.7.6"],"introduced":["0"],"last_affected":[],"package":"github.com/modelcontextprotocol/registry","purl":"pkg:golang/github.com/modelcontextprotocol/registry","source":"GHSA-95c3-6vvw-4mrq"},{"ecosystem":"Go","fixed":["1.7.6"],"introduced":["0"],"last_affected":[],"package":"github.com/modelcontextprotocol/registry","purl":"pkg:golang/github.com/modelcontextprotocol/registry","source":"GO-2026-5273"}],"prev":{"headline":"MCP Registry: Open Redirect","id":"CVE-2026-44427"},"products":["registry"],"published":"2026-05-14","related":[{"cvss_score":6.3,"headline":"MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist","id":"CVE-2026-44430","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":5.1,"headline":"MCP Registry: Stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`","id":"CVE-2026-44429","kev_date_added":null,"published":"2026-05-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-15","vendors":["modelcontextprotocol"]},"summary":"Attackers can replay GitHub OIDC tokens across different MCP Registry deployments to gain unauthorized publish permissions due to shared audience validation.","url":"https://insights.sbomify.com/CVE-2026-44428/"}