CVE-2026-23992
Published: July 22, 2026Last modified: July 30, 2026
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.
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.5 |
| Attack Vector | NETWORK |
| Attack complexity | LOW |
| Privileges required | NONE |
| User interaction | NONE |
| Scope | UNCHANGED |
| Confidentiality | NONE |
| Integrity impact | HIGH |
| Availability impact | NONE |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Notes
skopeo is not affected because it used go-tuf version < 2.0.0 docker-cli-buildx in 25 LTS is not affected because it doesn't use go-tuf dependency
Status
| Product | Release | Package | Status |
|---|---|---|---|
| Alpaquita Linux | 23 LTS | skopeo | Not affected (1.10.0-r2) |
| 25 LTS | docker-cli-buildx | Not affected (0.24.0-r0) | |
| skopeo | Not affected (1.18.0-r2) | ||
| Stream | docker-cli-buildx | Unknown (0.11.0-r0) | |
| skopeo | Not affected (1.13.0-r1) |