Back to CVE records
Medium 5.9Published Jan 21, 2026

CVE-2026-23992go-tuf improperly validates the configured threshold for delegations

Updated under an hour ago ()

Does this affect you?

It affects theupdateframework go-tuf and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.9 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness (CWE)
CWE-347
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Jan 22, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
theupdateframework go-tuf
theupdateframework:go_tuf (from the name)
from 2.0.0, < 2.3.1
CNA record
theupdateframework go-tuf
theupdateframework:go-tuf
from 2.0.0 before 2.3.1
NVD

References

  • x-refsource-confirm, patch, vendor-advisory
  • x-refsource-misc, patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.