# CVE-2026-23992: go-tuf improperly validates the configured threshold for delegations > A compromised TUF repository can set signature thresholds to zero, bypassing verification and allowing unauthorized modification of metadata files. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jan 2026 - **Updated:** 22 Jan 2026 - **Also known as:** AZL-75189, BELL-CVE-2026-23992, CLEANSTART-2026-PA71152, CLEANSTART-2026-UW62677, DEBIAN-CVE-2026-23992, GHSA-fphv-w9fq-2525, GO-2026-4349, MINI-26jj-67j2-w7x6, MINI-3mj3-mfgr-rq86, MINI-44w5-76gv-vfpx, MINI-4p9m-c473-rwxx, MINI-52wm-fjxx-3244, MINI-6gr6-v49f-79x3, MINI-85ph-hc68-mmxg, MINI-8g8v-c8qr-9wfq, MINI-9c8r-6jqw-9gq5, MINI-9x79-63wf-68fq, MINI-c2wj-xc4x-x2pp, MINI-cqpf-rh8v-mpp4, MINI-f39q-3mc4-978r, MINI-hg66-9g9c-2hq8, MINI-hqxj-5jx7-58hc, MINI-hv52-8843-23ff, MINI-hxp6-rpww-6v3h, MINI-jc8f-2wc8-p3xr, MINI-jq9g-66fp-g4vj, MINI-jr6w-q5hv-467g, MINI-pxhr-8h54-3g55, MINI-q44p-w9q4-xrf6, MINI-q774-xg66-3f38, MINI-qc98-ph29-m4g3, MINI-qfxr-66jc-4fx7, MINI-qrmf-fc55-h442, MINI-r46g-vr4j-3pm8, MINI-r7xx-m8j5-4h9g, MINI-rrvf-v2qw-hfq5, MINI-vfw7-6372-pc4q, MINI-vjh2-q8p5-ghvh, MINI-w39v-3vpc-q7pq, MINI-w7q3-964v-wq63, UBUNTU-CVE-2026-23992 ## What is CVE-2026-23992? CVE-2026-23992 is a medium-severity vulnerability in theupdateframework go-tuf, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-347 (Improper Verification of Cryptographic Signature) ## Which versions are affected by CVE-2026-23992? 3 open source packages ship an affected version, including github.com/theupdateframework/go-tuf/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/theupdateframework/go-tuf/v2` | Go | All versions | 2.3.1 | | `github.com/theupdateframework/go-tuf/v2` | Go | All versions | 2.3.1 | | `github.com/theupdateframework/go-tuf/v2` | Go | All versions | 2.3.1 | Products: Theupdateframework Go-Tuf. ## How do I fix CVE-2026-23992? Upgrade github.com/theupdateframework/go-tuf/v2 to 2.3.1 or later. ## Is CVE-2026-23992 being exploited? There is no known exploitation of CVE-2026-23992 in the wild and no public exploit code. ## Other vulnerabilities in theupdateframework go-tuf - [CVE-2022-29173](https://insights.sbomify.com/CVE-2022-29173/): No protection against rollback attacks in go-tuf (high 8.0) - [CVE-2026-23991](https://insights.sbomify.com/CVE-2026-23991/): go-tuf affected by client DoS via malformed server response (medium 5.9) - [CVE-2026-24686](https://insights.sbomify.com/CVE-2026-24686/): go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names (medium 4.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-23992 and fix it if it is affected. What it is: CVE-2026-23992 is a medium-severity vulnerability in theupdateframework go-tuf, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-23992 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/theupdateframework/go-tuf/v2 (Go): affected all versions; fixed in 2.3.1 - github.com/theupdateframework/go-tuf/v2 (Go): affected all versions; fixed in 2.3.1 - github.com/theupdateframework/go-tuf/v2 (Go): affected all versions; fixed in 2.3.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-23992/ (Markdown: https://insights.sbomify.com/CVE-2026-23992/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23992 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23992 - OSV: https://osv.dev/vulnerability/CVE-2026-23992 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-23992/ Summaries are generated and may contain mistakes; the official description above is the record.