Metadata integrity bypass via unchecked signature threshold
Published Jan 22, 2026 · Updated Jan 22, 2026
Signature verification failure in The Update Framework go-tuf 2.0.0 through 2.3.0 allows attackers to modify TUF metadata via a repository. Metadata.VerifyDelegate compares the valid-signature count with an unvalidated role threshold, so zero or negative values let the check pass without any valid signature. Exploitation requires a compromised or misconfigured TUF repository and permits unauthorized metadata modification at rest or in transit.
Summary
What happened
Signature verification failure in The Update Framework go-tuf 2.0.0 through 2.3.0 allows attackers to modify TUF metadata via a repository. Metadata.VerifyDelegate compares the valid-signature count with an unvalidated role threshold, so zero or negative values let the check pass without any valid signature. Exploitation requires a compromised or misconfigured TUF repository and permits unauthorized metadata modification at rest or in transit.
The record
- CVE
- CVE-2026-23992
- Published
- Jan 22, 2026
- Updated
- Jan 22, 2026
- Vendor
- The Update Framework
- Product
- go-tuf
- Classifications
- CWE-347, T1553
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2026CVE publishedPublication date reported by the CVE source.
- Jan 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.0, < 2.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo