CVE-2026-23992 Details
Description
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, a compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. This can lead to unauthorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. Version 2.3.1 fixes the issue. As a workaround, always make sure that the TUF metadata roles are configured with a threshold of at least 1.
A vulnerability exists in go-tuf versions 2.0.0 prior to 2.3.1, where a compromised or misconfigured TUF repository can set the signature threshold for delegations to 0. This misconfiguration effectively disables signature verification, allowing unauthorized modifications to TUF metadata files both at rest and in transit, as no integrity checks are performed. The issue has been patched in version 2.3.1.
Users are advised to upgrade to go-tuf version 2.3.1 or later. As a workaround, ensure that TUF metadata roles are configured with a signature threshold of at least 1.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 22, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-347 | Improper Verification of Cryptographic Signature | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| theupdateframework go-tuf | >= 2.0.0, < 2.3.1 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 17, 2026 | Initial Analysis | [email protected] |
| Jan 22, 2026 | New CVE Received | [email protected] |