Security readout for executives and security teams
Plain-English summary
CVE-2026-23991 can make applications using go-tuf crash when they receive malformed TUF metadata from a repository, mirror, or cache. It does not allow data theft or code execution based on current sources, but it can interrupt update workflows. The issue affects go-tuf versions 2.0.0 through before 2.3.1 and is fixed in 2.3.1.
Executive priority
Treat as a timely maintenance fix, especially for products where update availability is business-critical. It is not currently evidenced as exploited or code-execution capable, but a compromised mirror or cache could disrupt client update operations.
Technical view
go-tuf clients panic while parsing valid JSON that is not well-formed TUF metadata. The panic occurs before signature validation, so a compromised repository, mirror, or cache can cause client denial of service without signing keys. CVSS is 5.9, with network attack vector, high complexity, no privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is limited to software that embeds or depends on theupdateframework/go-tuf versions >=2.0.0 and <2.3.1. Systems that fetch TUF metadata through mirrors, caches, or repositories outside direct control have the clearest operational risk.
Exploitation context
The source advisory describes a denial-of-service condition from malformed server responses. The CVE is not in KEV, and the provided sources do not report active exploitation. Exploitation requires influence over a repository, mirror, cache, or equivalent metadata response path.
Researcher notes
Key nuance: signature validation does not protect against this crash because parsing fails first. The vulnerability maps to CWE-617 and CWE-754. Public sources identify the fixing release and commit, but do not provide evidence of exploitation or workaround options.
Mitigation direction
- Upgrade go-tuf to version 2.3.1 or later.
- Identify applications and services that embed vulnerable go-tuf versions.
- Review use of third-party mirrors, caches, or repositories in update paths.
- If immediate upgrade is not possible, check vendor guidance; sources list no workaround.
Validation and detection
- Inventory Go dependencies for theupdateframework/go-tuf versions >=2.0.0 and <2.3.1.
- Confirm production builds use go-tuf 2.3.1 or later.
- Map TUF metadata sources, mirrors, and caches used by affected clients.
- Monitor affected clients for unexpected panics or update-service availability failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-617: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-754: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23991 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324CVE reference · x_refsource_CONFIRM
- https://github.com/theupdateframework/go-tuf/commit/73345ab6b0eb7e59d525dac17a428f043074cef6CVE reference · x_refsource_MISC
- https://github.com/theupdateframework/go-tuf/releases/tag/v2.3.1CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.