FlawAtlas
Search the atlas
CVE-2026-23992 Moderate

Improper validattion of configured threshold for delegations in github.com/theupdateframework/go-tuf

Improper validattion of configured threshold for delegations in github.com/theupdateframework/go-tuf

Exploit probability 0.2%
Published February 2, 2026
Required by Not available
Last source change February 26, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

7 explicit affected versions

Go github.com/theupdateframework/go-tuf/v2
Go github.com/theupdateframework/go-tuf/v2

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-23992

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.

View original source
Open Source Vulnerabilities GO-2026-4349

Improper validattion of configured threshold for delegations in github.com/theupdateframework/go-tuf

View original source
Open Source Vulnerabilities GHSA-fphv-w9fq-2525

# Security Disclosure: Improper validation of configured threshold for delegations ## Summary A compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. ## Impact Unathorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. ## Patches Upgrade to v2.3.1 ## Workarounds Always make sure that the TUF metadata roles are configured with a threshold of at least 1. ## Affected code: The `metadata.VerifyDelegate` did not verify the configured threshold prior to comparison. This means that a misconfigured TUF repository could disable the signature verification by setting the threshold to 0, or a negative value (and so always make the signature threshold computation to pass).

View original source

05 / REFERENCES

Further evidence