CVE-2026-23991: go-tuf affected by client DoS via malformed server response
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.
Published Jan 21, 2026 · Updated Jan 22, 2026
Affected packages
github.com/theupdateframework/go-tuf/v2
- Ecosystem
- Go
- Affected
- < 2.3.1
- Fixed in
- 2.3.1
- Check
go list -m github.com/theupdateframework/go-tuf/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to 1seal, kommendorkapten, rdimitrov.
References
- https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324
- https://github.com/theupdateframework/go-tuf/releases/tag/v2.3.1
- https://github.com/theupdateframework/go-tuf/commit/73345ab6b0eb7e59d525dac17a428f043074cef6
- https://nvd.nist.gov/vuln/detail/CVE-2026-23991
- https://github.com/advisories/GHSA-846p-jg2w-w324
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-24686
go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names
medium4.7Jan 26, 2026CVE-2026-23992
go-tuf improperly validates the configured threshold for delegations
medium5.9Jan 21, 2026CVE-2024-47534
Incorrect delegation lookups can make go-tuf download the wrong artifact
high7.5Oct 1, 2024
