Directory Traversal Affecting cosign package, versions <3.0.4-r2


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Directory Traversal vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-COSIGN-15235999
  • published6 Feb 2026
  • disclosed27 Jan 2026

Introduced: 27 Jan 2026

CVE-2026-24686  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Chainguard cosign to version 3.0.4-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cosign package and not the cosign package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1