Snyk - Open Source Security

Snyk test report

April 26th 2026, 12:42:57 am (UTC+00:00)

Scanned the following paths:
  • quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd/Dockerfile (deb)
  • quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3//usr/local/bin/argocd (gomodules)
  • quay.io/argoproj/argocd:v3.4.0-rc6//usr/local/bin/git-lfs (gomodules)
  • quay.io/argoproj/argocd:v3.4.0-rc6//usr/local/bin/kustomize (gomodules)
  • quay.io/argoproj/argocd:v3.4.0-rc6/helm/v3//usr/local/bin/helm (gomodules)
73 known vulnerabilities
197 vulnerable dependency paths
2363 dependencies

Untrusted Search Path

high severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: go.opentelemetry.io/otel/sdk/resource
  • Introduced through: github.com/argoproj/argo-cd/v3@* and go.opentelemetry.io/otel/sdk/resource@v1.42.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* go.opentelemetry.io/otel/sdk/resource@v1.42.0

Overview

Affected versions of this package are vulnerable to Untrusted Search Path through the hostIDReaderBSD.read function in sdk/resource/host_id.go. An attacker can execute a malicious kenv binary by placing it earlier in $PATH and triggering host ID detection on BSD or Solaris systems when /etc/hostid is absent. When an application initializes OpenTelemetry resource detection under those conditions, it runs the attacker-controlled command in the application's context, allowing local code execution and compromising the process running the Go application.

Remediation

Upgrade go.opentelemetry.io/otel/sdk/resource to version 1.43.0 or higher.

References


Authentication Bypass

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: util-linux/libblkid1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and util-linux/libblkid1@2.41-4ubuntu4.2

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 e2fsprogs@1.47.2-3ubuntu2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libmount1@2.41-4ubuntu4.2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libuuid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 e2fsprogs@1.47.2-3ubuntu2 util-linux/libuuid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libuuid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/liblastlog2-2@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/liblastlog2-2@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libmount1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libmount1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2 util-linux/libmount1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libsmartcols1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libsmartcols1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2 util-linux/libsmartcols1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/bsdutils@1:2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/login@1:4.16.0-2+really2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A flaw was found in util-linux. Improper hostname canonicalization in the login(1) utility, when invoked with the -h option, can modify the supplied remote hostname before setting PAM_RHOST. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.

Remediation

There is no fixed version for Ubuntu:25.10 util-linux.

References


Time-of-check Time-of-use (TOCTOU)

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: util-linux/libblkid1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and util-linux/libblkid1@2.41-4ubuntu4.2

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 e2fsprogs@1.47.2-3ubuntu2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libmount1@2.41-4ubuntu4.2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2 util-linux/libblkid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libuuid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 e2fsprogs@1.47.2-3ubuntu2 util-linux/libuuid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libuuid1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/liblastlog2-2@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/liblastlog2-2@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libmount1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libmount1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2 util-linux/libmount1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/libsmartcols1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 util-linux/libsmartcols1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2 util-linux/libsmartcols1@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/bsdutils@1:2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/login@1:4.16.0-2+really2.41-4ubuntu4.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/mount@2.41-4ubuntu4.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.

Remediation

There is no fixed version for Ubuntu:25.10 util-linux.

References


Directory Traversal

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: tar
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and tar@1.35+dfsg-3.1build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 tar@1.35+dfsg-3.1build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 dpkg@1.22.21ubuntu3.1 tar@1.35+dfsg-3.1build1

NVD Description

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

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.

Remediation

There is no fixed version for Ubuntu:25.10 tar.

References


Unrestricted Upload of File with Dangerous Type

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: tar
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and tar@1.35+dfsg-3.1build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 tar@1.35+dfsg-3.1build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 dpkg@1.22.21ubuntu3.1 tar@1.35+dfsg-3.1build1

NVD Description

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

A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.

Remediation

There is no fixed version for Ubuntu:25.10 tar.

References


CVE-2026-35354

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the mv utility of uutils coreutils during cross-device moves. The extended attribute (xattr) preservation logic uses multiple path-based system calls that perform fresh path-to-inode lookups for each operation. A local attacker with write access to the directory can exploit this race to swap files between calls, causing the destination file to receive an inconsistent mix of security xattrs, such as SELinux labels or file capabilities.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35344

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The dd utility in uutils coreutils suppresses errors during file truncation operations by unconditionally calling Result::ok() on truncation attempts. While intended to mimic GNU behavior for special files like /dev/null, the uutils implementation also hides failures on regular files and directories caused by full disks or read-only file systems. This can lead to silent data corruption in backup or migration scripts, as the utility may report a successful operation even when the destination file contains old or garbage data.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35360

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The touch utility in uutils coreutils is vulnerable to a Time-of-Check to Time-of-Use (TOCTOU) race condition during file creation. When the utility identifies a missing path, it later attempts creation using File::create(), which internally uses O_TRUNC. An attacker can exploit this window to create a file or swap a symlink at the target path, causing touch to truncate an existing file and leading to permanent data loss.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35378

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the expr utility of uutils coreutils causes the program to evaluate parenthesized subexpressions during the parsing phase rather than at the execution phase. This implementation flaw prevents the utility from performing proper short-circuiting for logical OR (|) and AND (&) operations. As a result, arithmetic errors (such as division by zero) occurring within "dead" branches, branches that should be ignored due to short-circuiting, are raised as fatal errors. This divergence from GNU expr behavior can cause guarded expressions within shell scripts to fail with hard errors instead of returning expected boolean results, leading to premature script termination and breaking GNU-compatible shell control flow.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35361

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The mknod utility in uutils coreutils fails to handle security labels atomically by creating device nodes before setting the SELinux context. If labeling fails, the utility attempts cleanup using std::fs::remove_dir, which cannot remove device nodes or FIFOs. This leaves mislabeled nodes behind with incorrect default contexts, potentially allowing unauthorized access to device nodes that should have been restricted by mandatory access controls.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35345

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A vulnerability in the tail utility of uutils coreutils allows for the exfiltration of sensitive file contents when using the --follow=name option. Unlike GNU tail, the uutils implementation continues to monitor a path after it has been replaced by a symbolic link, subsequently outputting the contents of the link's target. In environments where a privileged user (e.g., root) monitors a log directory, a local attacker with write access to that directory can replace a log file with a symlink to a sensitive system file (such as /etc/shadow), causing tail to disclose the contents of the sensitive file.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35355

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The install utility in uutils coreutils is vulnerable to a Time-of-Check to Time-of-Use (TOCTOU) race condition during file installation. The implementation unlinks an existing destination file and then recreates it using a path-based operation without the O_EXCL flag. A local attacker can exploit the window between the unlink and the subsequent creation to swap the path with a symbolic link, allowing them to redirect privileged writes to overwrite arbitrary system files.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35379

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the tr utility of uutils coreutils causes the program to incorrectly define the [:graph:] and [:print:] character classes. The implementation mistakenly includes the ASCII space character (0x20) in the [:graph:] class and excludes it from the [:print:] class, effectively reversing the standard behavior established by POSIX and GNU coreutils. This vulnerability leads to unintended data modification or loss when the utility is used in automated scripts or data-cleaning pipelines that rely on standard character class semantics. For example, a command executed to delete all graphical characters while intending to preserve whitespace will incorrectly delete all ASCII spaces, potentially resulting in data corruption or logic failures in downstream processing.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35366

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The printenv utility in uutils coreutils fails to display environment variables containing invalid UTF-8 byte sequences. While POSIX permits arbitrary bytes in environment strings, the uutils implementation silently skips these entries rather than printing the raw bytes. This vulnerability allows malicious environment variables (e.g., adversarial LD_PRELOAD values) to evade inspection by administrators or security auditing tools, potentially allowing library injection or other environment-based attacks to go undetected.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35376

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the chcon utility of uutils coreutils during recursive operations. The implementation resolves recursive targets using a fresh path lookup (via fts_accpath) rather than binding the traversal and label application to the specific directory state encountered during traversal. Because these operations are not anchored to file descriptors, a local attacker with write access to a directory tree can exploit timing-sensitive rename or symbolic link races to redirect a privileged recursive relabeling operation to unintended files or directories. This vulnerability breaks the hardening expectations for SELinux administration workflows and can lead to the unauthorized modification of security labels on sensitive system objects.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35374

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the split utility of uutils coreutils. The program attempts to prevent data loss by checking for identity between input and output files using their file paths before initiating the split operation. However, the utility subsequently opens the output file with truncation after this path-based validation is complete. A local attacker with write access to the directory can exploit this race window by manipulating mutable path components (e.g., swapping a path with a symbolic link). This can cause split to truncate and write to an unintended target file, potentially including the input file itself or other sensitive files accessible to the process, leading to permanent data loss.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35340

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A flaw in the ChownExecutor used by uutils coreutils chown and chgrp causes the utilities to return an incorrect exit code during recursive operations. The final exit code is determined only by the last file processed. If the last operation succeeds, the command returns 0 even if earlier ownership or group changes failed due to permission errors. This can lead to security misconfigurations where administrative scripts incorrectly assume that ownership has been successfully transferred across a directory tree.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35375

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the split utility of uutils coreutils causes the corruption of output filenames when provided with non-UTF-8 prefix or suffix inputs. The implementation utilizes to_string_lossy() when constructing chunk filenames, which automatically rewrites invalid byte sequences into the UTF-8 replacement character (U+FFFD). This behavior diverges from GNU split, which preserves raw pathname bytes intact. In environments utilizing non-UTF-8 encodings, this vulnerability leads to the creation of files with incorrect names, potentially causing filename collisions, broken automation, or the misdirection of output data.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35341

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A vulnerability in uutils coreutils mkfifo allows for the unauthorized modification of permissions on existing files. When mkfifo fails to create a FIFO because a file already exists at the target path, it fails to terminate the operation for that path and continues to execute a follow-up set_permissions call. This results in the existing file's permissions being changed to the default mode (often 644 after umask), potentially exposing sensitive files such as SSH private keys to other users on the system.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35348

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The sort utility in uutils coreutils is vulnerable to a process panic when using the --files0-from option with inputs containing non-UTF-8 filenames. The implementation enforces UTF-8 encoding and utilizes expect(), causing an immediate crash when encountering valid but non-UTF-8 paths. This diverges from GNU sort, which treats filenames as raw bytes. A local attacker can exploit this to crash the utility and disrupt automated pipelines.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35356

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the install utility of uutils coreutils when using the -D flag. The command creates parent directories and subsequently performs a second path resolution to create the target file, neither of which is anchored to a directory file descriptor. An attacker with concurrent write access can replace a path component with a symbolic link between these operations, redirecting the privileged write to an arbitrary file system location.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35357

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The cp utility in uutils coreutils is vulnerable to an information disclosure race condition. Destination files are initially created with umask-derived permissions (e.g., 0644) before being restricted to their final mode (e.g., 0600) later in the process. A local attacker can race to open the file during this window; once obtained, the file descriptor remains valid and readable even after the permissions are tightened, exposing sensitive or private file contents.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35349

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A vulnerability in the rm utility of uutils coreutils allows a bypass of the --preserve-root protection. The implementation uses a path-string check rather than comparing device and inode numbers to identify the root directory. An attacker or accidental user can bypass this safeguard by using a symbolic link that resolves to the root directory (e.g., /tmp/rootlink -> /), potentially leading to the unintended recursive deletion of the entire root filesystem.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35377

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the env utility of uutils coreutils causes a failure to correctly parse command-line arguments when utilizing the -S (split-string) option. In GNU env, backslashes within single quotes are treated literally (with the exceptions of \ and '). However, the uutils implementation incorrectly attempts to validate these sequences, resulting in an "invalid sequence" error and an immediate process termination with an exit status of 125 when encountering valid but unrecognized sequences like \a or \x. This divergence from GNU behavior breaks compatibility for automated scripts and administrative workflows that rely on standard split-string semantics, leading to a local denial of service for those operations.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35367

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The nohup utility in uutils coreutils creates its default output file, nohup.out, without specifying explicit restricted permissions. This causes the file to inherit umask-based permissions, typically resulting in a world-readable file (0644). In multi-user environments, this allows any user on the system to read the captured stdout/stderr output of a command, potentially exposing sensitive information. This behavior diverges from GNU coreutils, which creates nohup.out with owner-only (0600) permissions.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35358

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The cp utility in uutils coreutils, when performing recursive copies (-R), incorrectly treats character and block device nodes as stream sources rather than preserving them. Because the implementation reads bytes into regular files at the destination instead of using mknod, device semantics are destroyed (e.g., /dev/null becomes a regular file). This behavior can lead to runtime denial of service through disk exhaustion or process hangs when reading from unbounded device nodes.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35364

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) race condition exists in the mv utility of uutils coreutils during cross-device operations. The utility removes the destination path before recreating it through a copy operation. A local attacker with write access to the destination directory can exploit this window to replace the destination with a symbolic link. The subsequent privileged move operation will follow the symlink, allowing the attacker to redirect the write and overwrite an arbitrary target file with contents from the source.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35359

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability in the cp utility of uutils coreutils allows an attacker to bypass no-dereference intent. The utility checks if a source path is a symbolic link using path-based metadata but subsequently opens it without the O_NOFOLLOW flag. An attacker with concurrent write access can swap a regular file for a symbolic link during this window, causing a privileged cp process to copy the contents of arbitrary sensitive files into a destination controlled by the attacker.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35365

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The mv utility in uutils coreutils improperly handles directory trees containing symbolic links during moves across filesystem boundaries. Instead of preserving symlinks, the implementation expands them, copying the linked targets as real files or directories at the destination. This can lead to resource exhaustion (disk space or time) if symlinks point to large external directories, unexpected duplication of sensitive data into unintended locations, or infinite recursion and repeated copying in the presence of symlink loops.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35371

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The id utility in uutils coreutils exhibits incorrect behavior in its "pretty print" output when the real UID and effective UID differ. The implementation incorrectly uses the effective GID instead of the effective UID when performing a name lookup for the effective user. This results in misleading diagnostic output that can cause automated scripts or system administrators to make incorrect decisions regarding file permissions or access control.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35370

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The id utility in uutils coreutils miscalculates the groups= section of its output. The implementation uses a user's real GID instead of their effective GID to compute the group list, leading to potentially divergent output compared to GNU coreutils. Because many scripts and automated processes rely on the output of id to make security-critical access-control or permission decisions, this discrepancy can lead to unauthorized access or security misconfigurations.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35342

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The mktemp utility in uutils coreutils fails to properly handle an empty TMPDIR environment variable. Unlike GNU mktemp, which falls back to /tmp when TMPDIR is an empty string, the uutils implementation treats the empty string as a valid path. This causes temporary files to be created in the current working directory (CWD) instead of the intended secure temporary directory. If the CWD is more permissive or accessible to other users than /tmp, it may lead to unintended information disclosure or unauthorized access to temporary data.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35352

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A Time-of-Check to Time-of-Use (TOCTOU) race condition exists in the mkfifo utility of uutils coreutils. The utility creates a FIFO and then performs a path-based chmod to set permissions. A local attacker with write access to the parent directory can swap the newly created FIFO for a symbolic link between these two operations. This redirects the chmod call to an arbitrary file, potentially enabling privilege escalation if the utility is run with elevated privileges.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35380

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the cut utility of uutils coreutils causes the program to incorrectly interpret the literal two-byte string '' (two single quotes) as an empty delimiter. The implementation mistakenly maps this string to the NUL character for both the -d (delimiter) and --output-delimiter options. This vulnerability can lead to silent data corruption or logic errors in automated scripts and data pipelines that process strings containing these characters, as the utility may unintentionally split or join data on NUL bytes rather than the intended literal characters.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35343

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The cut utility in uutils coreutils incorrectly handles the -s (only-delimited) option when a newline character is specified as the delimiter. The implementation fails to verify the only_delimited flag in the cut_fields_newline_char_delim function, causing the utility to print non-delimited lines that should have been suppressed. This can lead to unexpected data being passed to downstream scripts that rely on strict output filtering.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35381

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the cut utility of uutils coreutils causes the utility to ignore the -s (only-delimited) flag when using the -z (null-terminated) and -d '' (empty delimiter) options together. The implementation incorrectly routes this specific combination through a specialized newline-delimiter code path that fails to check the record suppression status. Consequently, uutils cut emits the entire record plus a NUL byte instead of suppressing it. This divergence from GNU coreutils behavior creates a data integrity risk for automated pipelines that rely on cut -s to filter out undelimited data.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35362

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The safe_traversal module in uutils coreutils, which provides protection against Time-of-Check to Time-of-Use (TOCTOU) symlink races using file-descriptor-relative syscalls, is incorrectly limited to Linux targets. On other Unix-like systems such as macOS and FreeBSD, the utility fails to utilize these protections, leaving directory traversal operations vulnerable to symlink race conditions.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35353

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The mkdir utility in uutils coreutils incorrectly applies permissions when using the -m flag by creating a directory with umask-derived permissions (typically 0755) before subsequently changing them to the requested mode via a separate chmod system call. In multi-user environments, this introduces a brief window where a directory intended to be private is accessible to other users, potentially leading to unauthorized data access.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35363

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A vulnerability in the rm utility of uutils coreutils allows the bypass of safeguard mechanisms intended to protect the current directory. While the utility correctly refuses to delete . or .., it fails to recognize equivalent paths with trailing slashes, such as ./ or .///. An accidental or malicious execution of rm -rf ./ results in the silent recursive deletion of all contents within the current directory. The command further obscures the data loss by reporting a misleading 'Invalid input' error, which may cause users to miss the critical window for data recovery.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35351

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The mv utility in uutils coreutils fails to preserve file ownership during moves across different filesystem boundaries. The utility falls back to a copy-and-delete routine that creates the destination file using the caller's UID/GID rather than the source's metadata. This flaw breaks backups and migrations, causing files moved by a privileged user (e.g., root) to become root-owned unexpectedly, which can lead to information disclosure or restricted access for the intended owners.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35347

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The comm utility in uutils coreutils incorrectly consumes data from non-regular file inputs before performing comparison operations. The are_files_identical function opens and reads from both input paths to compare content without first verifying if the paths refer to regular files. If an input path is a FIFO or a pipe, this pre-read operation drains the stream, leading to silent data loss before the actual comparison logic is executed. Additionally, the utility may hang indefinitely if it attempts to pre-read from infinite streams like /dev/zero.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35369

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

An argument parsing error in the kill utility of uutils coreutils incorrectly interprets kill -1 as a request to send the default signal (SIGTERM) to PID -1. Sending a signal to PID -1 causes the kernel to terminate all processes visible to the caller, potentially leading to a system crash or massive process termination. This differs from GNU coreutils, which correctly recognizes -1 as a signal number in this context and would instead report a missing PID argument.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35368

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A vulnerability exists in the chroot utility of uutils coreutils when using the --userspec option. The utility resolves the user specification via getpwnam() after entering the chroot but before dropping root privileges. On glibc-based systems, this can trigger the Name Service Switch (NSS) to load shared libraries (e.g., libnss_*.so.2) from the new root directory. If the NEWROOT is writable by an attacker, they can inject a malicious NSS module to execute arbitrary code as root, facilitating a full container escape or privilege escalation.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35350

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The cp utility in uutils coreutils fails to properly handle setuid and setgid bits when ownership preservation fails. When copying with the -p (preserve) flag, the utility applies the source mode bits even if the chown operation is unsuccessful. This can result in a user-owned copy retaining original privileged bits, creating unexpected privileged executables that violate local security policies. This differs from GNU cp, which clears these bits when ownership cannot be preserved.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35338

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A vulnerability in the chmod utility of uutils coreutils allows users to bypass the --preserve-root safety mechanism. The implementation only validates if the target path is literally / and does not canonicalize the path. An attacker or accidental user can use path variants such as /../ or symbolic links to execute destructive recursive operations (e.g., chmod -R 000) on the entire root filesystem, leading to system-wide permission loss and potential complete system breakdown.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35339

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The recursive mode (-R) of the chmod utility in uutils coreutils incorrectly handles exit codes when processing multiple files. The final return value is determined solely by the success or failure of the last file processed. This allows the command to return an exit code of 0 (success) even if errors were encountered on previous files, such as 'Operation not permitted'. Scripts relying on these exit codes may proceed under a false sense of success while sensitive files remain with restrictive or incorrect permissions.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35346

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

The comm utility in uutils coreutils silently corrupts data by performing lossy UTF-8 conversion on all output lines. The implementation uses String::from_utf8_lossy(), which replaces invalid UTF-8 byte sequences with the Unicode replacement character (U+FFFD). This behavior differs from GNU comm, which processes raw bytes and preserves the original input. This results in corrupted output when the utility is used to compare binary files or files using non-UTF-8 legacy encodings.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35372

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the ln utility of uutils coreutils allows the utility to dereference a symbolic link target even when the --no-dereference (or -n) flag is explicitly provided. The implementation previously only honored the "no-dereference" intent if the --force (overwrite) mode was also enabled. This flaw causes ln to follow a symbolic link that points to a directory and create new links inside that target directory instead of treating the symbolic link itself as the destination. In environments where a privileged user or system script uses ln -n to update a symlink, a local attacker could manipulate existing symbolic links to redirect file creation into sensitive directories, potentially leading to unauthorized file creation or system misconfiguration.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


CVE-2026-35373

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: rust-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and rust-coreutils@0.2.2-0ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 rust-coreutils@0.2.2-0ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 rust-coreutils@0.2.2-0ubuntu2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.10 relevant fixed versions and status.

A logic error in the ln utility of uutils coreutils causes the program to reject source paths containing non-UTF-8 filename bytes when using target-directory forms (e.g., ln SOURCE... DIRECTORY). While GNU ln treats filenames as raw bytes and creates the links correctly, the uutils implementation enforces UTF-8 encoding, resulting in a failure to stat the file and a non-zero exit code. In environments where automated scripts or system tasks process valid but non-UTF-8 filenames common on Unix filesystems, this divergence causes the utility to fail, leading to a local denial of service for those specific operations.

Remediation

There is no fixed version for Ubuntu:25.10 rust-coreutils.

References


Directory Traversal

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: pam/libpam0g
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and pam/libpam0g@1.7.0-5ubuntu2

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/login@1:4.16.0-2+really2.41-4ubuntu4.2 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2 pam/libpam-modules@1.7.0-5ubuntu2 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2 pam/libpam-modules@1.7.0-5ubuntu2 pam/libpam-modules-bin@1.7.0-5ubuntu2 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 pam/libpam-modules-bin@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2 pam/libpam-modules@1.7.0-5ubuntu2 pam/libpam-modules-bin@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 pam/libpam-runtime@1.7.0-5ubuntu2 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/login@1:4.16.0-2+really2.41-4ubuntu4.2 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 pam/libpam-runtime@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux@2.41-4ubuntu4.2 pam/libpam-runtime@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/login@1:4.16.0-2+really2.41-4ubuntu4.2 pam/libpam-runtime@1.7.0-5ubuntu2

NVD Description

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

A flaw was found in linux-pam. The pam_namespace module may improperly handle user-controlled paths, allowing local users to exploit symlink attacks and race conditions to elevate their privileges to root. This CVE provides a "complete" fix for CVE-2025-6020.

Remediation

There is no fixed version for Ubuntu:25.10 pam.

References


Improper Verification of Cryptographic Signature

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and gnupg2/gpgv@2.4.8-2ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg@2.4.8-2ubuntu2.1 gnupg2/gpgconf@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg-agent@2.4.8-2ubuntu2.1 gnupg2/gpgconf@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg-agent@2.4.8-2ubuntu2.1

NVD Description

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

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

Remediation

There is no fixed version for Ubuntu:25.10 gnupg2.

References


CVE-2026-4437

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: glibc/libc-bin
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and glibc/libc-bin@2.42-0ubuntu3.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 glibc/libc-bin@2.42-0ubuntu3.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 glibc/libc6@2.42-0ubuntu3.1

NVD Description

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

Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.

Remediation

There is no fixed version for Ubuntu:25.10 glibc.

References


CVE-2026-4438

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: glibc/libc-bin
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and glibc/libc-bin@2.42-0ubuntu3.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 glibc/libc-bin@2.42-0ubuntu3.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 glibc/libc6@2.42-0ubuntu3.1

NVD Description

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

Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.

Remediation

There is no fixed version for Ubuntu:25.10 glibc.

References


CVE-2026-4046

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: glibc/libc-bin
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and glibc/libc-bin@2.42-0ubuntu3.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 glibc/libc-bin@2.42-0ubuntu3.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 glibc/libc6@2.42-0ubuntu3.1

NVD Description

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

The iconv() function in the GNU C Library versions 2.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application.

This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.

Remediation

There is no fixed version for Ubuntu:25.10 glibc.

References


Improper Validation of Specified Type of Input

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/vmihailenco/msgpack/v5
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/vmihailenco/msgpack/v5@v5.4.1

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/vmihailenco/msgpack/v5@v5.4.1

Overview

Affected versions of this package are vulnerable to Improper Validation of Specified Type of Input in the calls plugin when handling websocket messages containing malformed msgpack frames. An attacker can cause the server to consume excessive memory and crash by sending specially crafted websocket requests.

Remediation

There is no fixed version for github.com/vmihailenco/msgpack/v5.

References


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/r3labs/diff/v3
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/r3labs/diff/v3@v3.0.2

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/r3labs/diff/v3@v3.0.2

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/hashicorp/go-version
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/hashicorp/go-version@v1.7.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/hashicorp/go-version@v1.7.0

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6 /usr/local/bin/git-lfs
  • Package Manager: golang
  • Module: github.com/hashicorp/go-uuid
  • Introduced through: go-distribution@command-line-arguments@* and github.com/hashicorp/go-uuid@v1.0.2

Detailed paths

  • Introduced through: go-distribution@command-line-arguments@* github.com/hashicorp/go-uuid@v1.0.2

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/hashicorp/go-retryablehttp
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/hashicorp/go-retryablehttp@v0.7.8

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/hashicorp/go-retryablehttp@v0.7.8

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/helm/v3 /usr/local/bin/helm
  • Package Manager: golang
  • Module: github.com/hashicorp/go-multierror
  • Introduced through: helm.sh/helm/v3@* and github.com/hashicorp/go-multierror@v1.1.1

Detailed paths

  • Introduced through: helm.sh/helm/v3@* github.com/hashicorp/go-multierror@v1.1.1

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/hashicorp/go-cleanhttp
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/hashicorp/go-cleanhttp@v0.5.2

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/hashicorp/go-cleanhttp@v0.5.2

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/gosimple/slug
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/gosimple/slug@v1.15.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/gosimple/slug@v1.15.0

MPL-2.0 license


Improper Validation of Integrity Check Value

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/go-git/go-git/v5/storage/filesystem
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/go-git/go-git/v5/storage/filesystem@v5.14.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/go-git/go-git/v5/storage/filesystem@v5.14.0

Overview

Affected versions of this package are vulnerable to Improper Validation of Integrity Check Value for .idx and .pack files. An attacker can cause the application to consume corrupted files, leading to unexpected errors, due to checksums not being checked in the loadIdxFile() function.

Workaround

This vulnerability can be mitigated by running 'git fsck' from the git CLI to check for data corruption on a given repository.

Remediation

Upgrade github.com/go-git/go-git/v5/storage/filesystem to version 5.16.5 or higher.

References


Insufficiently Protected Credentials

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/go-git/go-git/v5/plumbing/transport/http
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/go-git/go-git/v5/plumbing/transport/http@v5.14.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/go-git/go-git/v5/plumbing/transport/http@v5.14.0

Overview

Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the advertisedReferences() function. The headers - including Authorization headers - from an initial /info/refs request are forwarded to redirect targets. An attacker can obtain authentication credentials by controlling a redirect target, and those credentials may be reused on other endpoints or attempted against other repositories owned by the victim. This is only exploitable if the client interacts with untrusted or misconfigured remote servers, or uses HTTP (not HTTPS) connections.

Remediation

Upgrade github.com/go-git/go-git/v5/plumbing/transport/http to version 5.18.0 or higher.

References


Allocation of Resources Without Limits or Throttling

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/go-git/go-git/v5/plumbing/format/index
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/go-git/go-git/v5/plumbing/format/index@v5.14.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/go-git/go-git/v5/plumbing/format/index@v5.14.0

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the handling of .idx files. An attacker with write access to the local repository's .git directory can exhaust system memory by introducing a maliciously crafted .idx file into the .git directory.

Remediation

Upgrade github.com/go-git/go-git/v5/plumbing/format/index to version 5.17.1 or higher.

References


Improper Validation of Array Index

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/go-git/go-git/v5/plumbing/format/index
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/go-git/go-git/v5/plumbing/format/index@v5.14.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/go-git/go-git/v5/plumbing/format/index@v5.14.0

Overview

Affected versions of this package are vulnerable to Improper Validation of Array Index through improper validation in the index decoding for version 4 files. An attacker with write access to the .git directory to modify or inject the index file can cause a panic and terminate the process by supplying a maliciously crafted .git/index file that triggers an out-of-bounds slice operation during index parsing.

Remediation

Upgrade github.com/go-git/go-git/v5/plumbing/format/index to version 5.17.1 or higher.

References


Improper Encoding or Escaping of Output

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: git/git-man
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6, git@1:2.51.0-1ubuntu1 and others

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 git@1:2.51.0-1ubuntu1 git/git-man@1:2.51.0-1ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 git@1:2.51.0-1ubuntu1

NVD Description

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

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

Remediation

There is no fixed version for Ubuntu:25.10 git.

References


Algorithmic Complexity

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: expat/libexpat1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6, git@1:2.51.0-1ubuntu1 and others

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 git@1:2.51.0-1ubuntu1 expat/libexpat1@2.7.1-2ubuntu0.2

NVD Description

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

In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.

Remediation

There is no fixed version for Ubuntu:25.10 expat.

References


CVE-2026-2219

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: dpkg
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and dpkg@1.22.21ubuntu3.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 dpkg@1.22.21ubuntu3.1

NVD Description

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

It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).

Remediation

There is no fixed version for Ubuntu:25.10 dpkg.

References


CVE-2024-56433

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: shadow/login.defs
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and shadow/login.defs@1:4.17.4-2ubuntu2

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 shadow/login.defs@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 util-linux/login@1:4.16.0-2+really2.41-4ubuntu4.2 shadow/login.defs@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2 shadow/login.defs@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 shadow/passwd@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 openssh/openssh-client@1:10.0p1-5ubuntu5.1 shadow/passwd@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 adduser@3.152ubuntu1 shadow/passwd@1:4.17.4-2ubuntu2

NVD Description

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

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Remediation

There is no fixed version for Ubuntu:25.10 shadow.

References


Covert Timing Channel

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: libgcrypt20
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and libgcrypt20@1.11.0-7build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg@2.4.8-2ubuntu2.1 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg-agent@2.4.8-2ubuntu2.1 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 gnupg2/gpgv@2.4.8-2ubuntu2.1 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg@2.4.8-2ubuntu2.1 gnupg2/gpgconf@2.4.8-2ubuntu2.1 libgcrypt20@1.11.0-7build1

NVD Description

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

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Ubuntu:25.10 libgcrypt20.

References


Out-of-bounds Write

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and gnupg2/gpgv@2.4.8-2ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 apt@3.1.6ubuntu2 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg@2.4.8-2ubuntu2.1 gnupg2/gpgconf@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg-agent@2.4.8-2ubuntu2.1 gnupg2/gpgconf@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 gnupg2/gpg-agent@2.4.8-2ubuntu2.1

NVD Description

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

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Ubuntu:25.10 gnupg2.

References


Improper Input Validation

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc6/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: coreutils/gnu-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 and coreutils/gnu-coreutils@9.5-1ubuntu4.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils/gnu-coreutils@9.5-1ubuntu4.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 tzdata@2026a-0ubuntu0.25.10.1 coreutils/gnu-coreutils@9.5-1ubuntu4.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc6 coreutils-from/coreutils@9.5-1ubuntu2+0.0.0~ubuntu24 coreutils-from/coreutils-from-uutils@0.0.0~ubuntu24 coreutils/gnu-coreutils@9.5-1ubuntu4.1

NVD Description

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

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

Remediation

There is no fixed version for Ubuntu:25.10 coreutils.

References