Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
go-tuf (github.com/theupdateframework/go-tuf/v2) versions before 2.3.1 can panic while parsing TUF metadata that a repository, mirror, or cache returns, because the metadata type check does not safely handle malformed input. An attacker who can serve such a response does not need any signing key, and the panic happens before signature validation, so clients can crash and long-running services may enter a restart loop. Upgrade to go-tuf v2.3.1 or later. No workaround is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0058, the 48th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-846p-jg2w-w324
- OSV: GHSA-846p-jg2w-w324
- github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324
- nvd.nist.gov/vuln/detail/CVE-2026-23991
- github.com/theupdateframework/go-tuf/commit/73345ab6b0eb7e59d525dac17a428f043074cef6
- github.com/theupdateframework/go-tuf
- github.com/theupdateframework/go-tuf/releases/tag/v2.3.1