Rdimitrov

**Name of the Vulnerable Software and Affected Versions** MCP Registry versions prior to 1.7.9 **Description** OCI ownership validation fails to perform a label-match check when an upstream OCI registry returns an HTTP 429 (Too Many Requests) error. This occurs because the function `ValidateOCI()` in the file `internal/validators/registries/oci.go` fails open during rate-limiting events. Consequently, any authenticated publisher can bind their `io.github.<user>/*` namespace to OCI images they do not control, bypassing the `io.modelcontextprotocol.server.name` label-match check, which serves as the sole cross-system ownership proof for OCI packages. **Recommendations** Update to version 1.7.9.

**Name of the Vulnerable Software and Affected Versions** go-tuf versions prior to 0.3.0 **Description** The issue concerns the client workflow for updating metadata files for roles other than the root role in go-tuf, a Go implementation of The Update Framework (TUF). Specifically, checks for rollback attacks are not implemented correctly, allowing an attacker to cause clients to install software that is older than the software the client previously knew to be available, potentially including software with known vulnerabilities. The client code has several issues: it does not consider previously trusted metadata before updating roles other than the root role, and it saves timestamp and snapshot metadata files as trusted before verifying their version correctness. **Recommendations** For versions prior to 0.3.0, upgrade to version 0.3.0 or newer to resolve the issue. As a temporary workaround, consider restricting the use of the vulnerable client workflow until a patch is available. No other workarounds are known apart from upgrading.