Debian Package Tracker
Register | Log in
Subscribe

golang-github-theupdateframework-go-tuf

Securing software in golang (library)

Choose email to subscribe with

general
  • source: golang-github-theupdateframework-go-tuf (main)
  • version: 2.3.0+0.7.0-1
  • maintainer: Debian Go Packaging Team (DMD)
  • uploaders: Reinhard Tartler [DMD] – Simon Josefsson [DMD]
  • arch: all
  • std-ver: 4.7.3
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • old-bpo: 0.5.2-5~bpo12+1
  • stable: 2.0.2+0.7.0-1
  • testing: 2.3.0+0.7.0-1
  • unstable: 2.3.0+0.7.0-1
versioned links
  • 0.5.2-5~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.0.2+0.7.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.3.0+0.7.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • golang-github-theupdateframework-go-tuf-dev
action needed
A new upstream version is available: 2.4.1 high
A new upstream version 2.4.1 is available, you should consider packaging it.
Created: 2026-01-23 Last update: 2026-02-01 05:01
3 security issues in trixie high

There are 3 open security issues in trixie.

2 important issues:
  • CVE-2026-23991: go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
  • CVE-2026-23992: 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.
1 issue left for the package maintainer to handle:
  • CVE-2026-24686: (needs triaging) go-tuf is a Go implementation of The Update Framework (TUF). go-tuf's TAP 4 Multirepo Client uses the map file repository name string (`repoName`) as a filesystem path component when selecting the local metadata cache directory. Starting in version 2.0.0 and prior to version 2.4.1, if an application accepts a map file from an untrusted source, an attacker can supply a `repoName` containing traversal (e.g., `../escaped-repo`) and cause go-tuf to create directories and write the root metadata file outside the intended `LocalMetadataDir` cache base, within the running process's filesystem permissions. Version 2.4.1 contains a patch.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-01-23 Last update: 2026-01-31 18:02
3 security issues in sid high

There are 3 open security issues in sid.

3 important issues:
  • CVE-2026-23991: go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
  • CVE-2026-23992: 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.
  • CVE-2026-24686: go-tuf is a Go implementation of The Update Framework (TUF). go-tuf's TAP 4 Multirepo Client uses the map file repository name string (`repoName`) as a filesystem path component when selecting the local metadata cache directory. Starting in version 2.0.0 and prior to version 2.4.1, if an application accepts a map file from an untrusted source, an attacker can supply a `repoName` containing traversal (e.g., `../escaped-repo`) and cause go-tuf to create directories and write the root metadata file outside the intended `LocalMetadataDir` cache base, within the running process's filesystem permissions. Version 2.4.1 contains a patch.
Created: 2026-01-23 Last update: 2026-01-31 18:02
3 security issues in forky high

There are 3 open security issues in forky.

3 important issues:
  • CVE-2026-23991: go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
  • CVE-2026-23992: 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.
  • CVE-2026-24686: go-tuf is a Go implementation of The Update Framework (TUF). go-tuf's TAP 4 Multirepo Client uses the map file repository name string (`repoName`) as a filesystem path component when selecting the local metadata cache directory. Starting in version 2.0.0 and prior to version 2.4.1, if an application accepts a map file from an untrusted source, an attacker can supply a `repoName` containing traversal (e.g., `../escaped-repo`) and cause go-tuf to create directories and write the root metadata file outside the intended `LocalMetadataDir` cache base, within the running process's filesystem permissions. Version 2.4.1 contains a patch.
Created: 2026-01-23 Last update: 2026-01-31 18:02
news
[rss feed]
  • [2026-01-06] golang-github-theupdateframework-go-tuf 2.3.0+0.7.0-1 MIGRATED to testing (Debian testing watch)
  • [2026-01-03] Accepted golang-github-theupdateframework-go-tuf 2.3.0+0.7.0-1 (source) into unstable (Simon Josefsson)
  • [2024-12-14] golang-github-theupdateframework-go-tuf 2.0.2+0.7.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-12-12] Accepted golang-github-theupdateframework-go-tuf 2.0.2+0.7.0-1 (source) into unstable (Simon Josefsson)
  • [2024-12-01] Accepted golang-github-theupdateframework-go-tuf 2.0.2+0.7.0-1~exp0 (source) into experimental (Simon Josefsson)
  • [2024-10-27] golang-github-theupdateframework-go-tuf 2.0.2-1 MIGRATED to testing (Debian testing watch)
  • [2024-10-25] Accepted golang-github-theupdateframework-go-tuf 2.0.2-1 (source) into unstable (Simon Josefsson)
  • [2024-10-23] Accepted golang-github-theupdateframework-go-tuf 2.0.2-1~exp0 (source) into experimental (Simon Josefsson)
  • [2023-11-23] golang-github-theupdateframework-go-tuf 0.6.1-1 MIGRATED to testing (Debian testing watch)
  • [2023-11-21] Accepted golang-github-theupdateframework-go-tuf 0.6.1-1 (source) into unstable (Reinhard Tartler)
  • [2023-11-01] Accepted golang-github-theupdateframework-go-tuf 0.5.2-5~bpo12+1 (source all) into stable-backports (Debian FTP Masters) (signed by: Nilesh Patra)
  • [2023-09-15] golang-github-theupdateframework-go-tuf 0.5.2-5 MIGRATED to testing (Debian testing watch)
  • [2023-09-15] golang-github-theupdateframework-go-tuf 0.5.2-5 MIGRATED to testing (Debian testing watch)
  • [2023-09-12] Accepted golang-github-theupdateframework-go-tuf 0.5.2-5 (source) into unstable (Reinhard Tartler)
  • [2023-08-23] Accepted golang-github-theupdateframework-go-tuf 0.5.2-3 (source) into unstable (Reinhard Tartler)
  • [2023-07-15] Accepted golang-github-theupdateframework-go-tuf 0.5.2-2 (all source) into experimental (Debian FTP Masters) (signed by: Reinhard Tartler)
bugs [bug history graph]
  • all: 3
  • RC: 0
  • I&N: 3
  • M&W: 0
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.0.2+0.7.0-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing