If the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a DoS. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key.
Client crashes upon receiving and parsing malformed TUF metadata. This can cause long running services to enter an restart/crash loop.
None currently.
The metadata.checkType function did not properly type assert the (untrusted) input causing it to panic on malformed data.
{
"github_reviewed": true,
"cwe_ids": [
"CWE-617",
"CWE-754"
],
"severity": "MODERATE",
"github_reviewed_at": "2026-01-21T16:19:28Z",
"nvd_published_at": "2026-01-22T03:15:47Z"
}