GHSA-fphv-w9fq-2525

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).

Database specific

{
    "nvd_published_at": "2026-01-22T03:15:47Z",
    "cwe_ids": [
        "CWE-347"
    ],
    "github_reviewed_at": "2026-01-21T16:19:32Z",
    "severity": "MODERATE",
    "github_reviewed": true
}

References

Affected packages

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

Package

Name: github.com/theupdateframework/go-tuf/v2; View open source insights on deps.dev
Purl: pkg:golang/github.com/theupdateframework/go-tuf/v2

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

2.3.1

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/01/GHSA-fphv-w9fq-2525/GHSA-fphv-w9fq-2525.json"