GHSA-846p-jg2w-w324
go-tuf affected by client DoS via malformed server response
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Go | github.com/theupdateframework/go-tuf/v2 | < 2.3.1 | 2.3.1 |
Details
As written in the advisory (Markdown source, shown as plain text).
# Security Disclosure: Client DoS via malformed server response
## Summary
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.
## Impact
Client crashes upon receiving and parsing malformed TUF metadata. This can cause long running services to enter an restart/crash loop.
## Workarounds
None currently.
## Affected code
The `metadata.checkType` function did not properly type assert the (untrusted) input causing it to panic on malformed data.
References
External links from the advisory. They lead to third-party sites.
- https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324
- https://nvd.nist.gov/vuln/detail/CVE-2026-23991
- https://github.com/theupdateframework/go-tuf/commit/73345ab6b0eb7e59d525dac17a428f043074cef6
- https://github.com/theupdateframework/go-tuf
- https://github.com/theupdateframework/go-tuf/releases/tag/v2.3.1