Snyk - Open Source Security

Snyk test report

March 29th 2026, 12:36:53 am (UTC+00:00)

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

CVE-2026-3184

medium severity
Exploit: Not Defined

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

Detailed paths

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

NVD Description

This vulnerability has not been analyzed by NVD yet.

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-rc3/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: tar
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 and tar@1.35+dfsg-3.1build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 tar@1.35+dfsg-3.1build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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


Directory Traversal

medium severity
Exploit: Not Defined

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

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 util-linux@2.41-4ubuntu4.2 pam/libpam0g@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3 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-rc3 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-rc3 pam/libpam-modules-bin@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 util-linux@2.41-4ubuntu4.2 pam/libpam-modules@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3 pam/libpam-runtime@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 util-linux@2.41-4ubuntu4.2 pam/libpam-runtime@1.7.0-5ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 and gnupg2/gpgv@2.4.8-2ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 apt@3.1.6ubuntu2 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3 gnupg2/gpg@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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


Improper Validation of Specified Type of Input

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.4.0-rc3/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-rc3/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-rc3/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-rc3 /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-rc3/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-rc3/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-rc3/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-rc3/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-rc3/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


Improper Encoding or Escaping of Output

medium severity
Exploit: Not Defined

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

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: expat/libexpat1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3, git@1:2.51.0-1ubuntu1 and others

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-2024-56433

low severity
Exploit: Not Defined

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

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 shadow/login.defs@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3 shadow/passwd@1:4.17.4-2ubuntu2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: libgcrypt20
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 and libgcrypt20@1.11.0-7build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 gnupg2/gpg@2.4.8-2ubuntu2.1 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 gnupg2/gpg-agent@2.4.8-2ubuntu2.1 libgcrypt20@1.11.0-7build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 and gnupg2/gpgv@2.4.8-2ubuntu2.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 apt@3.1.6ubuntu2 gnupg2/gpgv@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3 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-rc3 gnupg2/gpg@2.4.8-2ubuntu2.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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-rc3/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.10
  • Vulnerable module: coreutils/gnu-coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 and coreutils/gnu-coreutils@9.5-1ubuntu4.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 coreutils/gnu-coreutils@9.5-1ubuntu4.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 tzdata@2025b-3ubuntu1.1 coreutils/gnu-coreutils@9.5-1ubuntu4.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.4.0-rc3 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