CVE-2026-45781: CWE-636: Not Failing Securely ('Failing Open') in modelcontextprotocol registry
CVE-2026-45781 is a vulnerability in the modelcontextprotocol (MCP) registry prior to version 1. 7. 9. The issue arises because the OCI ownership validation fails open when the upstream OCI registry returns an HTTP 429 (Too Many Requests) response. This failure allows any authenticated publisher to bind namespaces they do not control to OCI images without proper ownership verification. The vulnerability is fixed in version 1. 7. 9. The CVSS score is 3. 5, indicating low severity.
AI Analysis
Technical Summary
The MCP Registry provides clients with a list of MCP servers and validates ownership of OCI images by checking label matches. In versions before 1.7.9, when the upstream OCI registry rate-limits anonymous fetches with HTTP 429, the validation function ValidateOCI incorrectly returns success without performing the critical label-match check. This 'fail open' behavior allows authenticated publishers to bind io.github.<user>/* namespaces to OCI images they do not own. Other registry types enforce stricter error handling by treating non-200 responses as hard errors. This flaw is addressed in MCP Registry version 1.7.9.
Potential Impact
The vulnerability allows authenticated publishers to bypass ownership validation for OCI images under certain rate-limiting conditions, potentially enabling unauthorized namespace bindings. The impact is limited to integrity (low impact) with no confidentiality or availability effects reported. Exploitation requires authentication and user interaction (UI:R). No known exploits are reported in the wild.
Mitigation Recommendations
This vulnerability is fixed in modelcontextprotocol registry version 1.7.9. Users should upgrade to version 1.7.9 or later to ensure proper ownership validation and prevent unauthorized namespace bindings. Since no official patch link or advisory is provided, verify upgrade availability from the vendor. Patch status is not yet confirmed via vendor advisory; check the vendor's official resources for current remediation guidance.
CVE-2026-45781: CWE-636: Not Failing Securely ('Failing Open') in modelcontextprotocol registry
Description
CVE-2026-45781 is a vulnerability in the modelcontextprotocol (MCP) registry prior to version 1. 7. 9. The issue arises because the OCI ownership validation fails open when the upstream OCI registry returns an HTTP 429 (Too Many Requests) response. This failure allows any authenticated publisher to bind namespaces they do not control to OCI images without proper ownership verification. The vulnerability is fixed in version 1. 7. 9. The CVSS score is 3. 5, indicating low severity.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The MCP Registry provides clients with a list of MCP servers and validates ownership of OCI images by checking label matches. In versions before 1.7.9, when the upstream OCI registry rate-limits anonymous fetches with HTTP 429, the validation function ValidateOCI incorrectly returns success without performing the critical label-match check. This 'fail open' behavior allows authenticated publishers to bind io.github.<user>/* namespaces to OCI images they do not own. Other registry types enforce stricter error handling by treating non-200 responses as hard errors. This flaw is addressed in MCP Registry version 1.7.9.
Potential Impact
The vulnerability allows authenticated publishers to bypass ownership validation for OCI images under certain rate-limiting conditions, potentially enabling unauthorized namespace bindings. The impact is limited to integrity (low impact) with no confidentiality or availability effects reported. Exploitation requires authentication and user interaction (UI:R). No known exploits are reported in the wild.
Mitigation Recommendations
This vulnerability is fixed in modelcontextprotocol registry version 1.7.9. Users should upgrade to version 1.7.9 or later to ensure proper ownership validation and prevent unauthorized namespace bindings. Since no official patch link or advisory is provided, verify upgrade availability from the vendor. Patch status is not yet confirmed via vendor advisory; check the vendor's official resources for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T07:45:21.252Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a063d1aec166c07b013014d
Added to database: 5/14/2026, 9:22:34 PM
Last enriched: 5/14/2026, 9:36:58 PM
Last updated: 5/14/2026, 10:23:49 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.