Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL

CVE-2026-55797GHSA-j6cw-g6p4-7hch

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-cd/v2

    Affected
    >= 2.11.0, <= 2.14.21
    Fixed in
    no fixed version recorded

  • Go github.com/argoproj/argo-cd/v3

    Affected
    >= 3.0.0, < 3.3.15>= 3.4.0, < 3.4.10>= 3.5.0, < 3.5.4>= 3.6.0-rc1, <= 3.6.0-rc1
    Fixed in
    3.5.4, 3.3.15, 3.6.0-rc2, 3.4.10

  • Go github.com/argoproj/argo-cd

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-55797: 1.87% estimated exploitation activity in the next 30 days; percentile 79.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Argo CD runs a shell command in the repo-server when it clones or fetches an SSH Git repository that has a proxy URL. The proxy host and port are copied into an SSH ProxyCommand. A host that contains shell metacharacters breaks out of that command and runs in the repo-server. All versions from v2.11.0 onward are affected, including every currently supported release. v2.10.20 and earlier are not. The behavior was introduced in 9b27aeb1a4 (2024-01-09, #15864), the change that added SOCKS5 proxy support for SSH Git URLs, and was first released in v2.11.0. The repository must use SSH. http, https, and socks5 proxy URLs all take this path when they are set on an SSH repository. An HTTPS Git repository uses the proxy as an HTTP proxy and does not build this command. Anyone who can create or update a repository or a repository credential template can set the proxy. That includes a project-scoped repository permission, argocd repo add --proxy, and a repository Secret. A credential…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-j6cw-g6p4-7hch

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6701

  3. Revision 1 · created ·

    Published from osv record GHSA-j6cw-g6p4-7hch

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55797

Advisory: Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL
IDs: CVE-2026-55797, GHSA-j6cw-g6p4-7hch
Record: https://patchnext.com/advisories/cve-2026-55797 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v3 3.6.0-rc2, 3.5.4, 3.4.10, 3.3.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.11.0, <= 2.14.21
- Go github.com/argoproj/argo-cd/v3: affected >= 3.0.0, < 3.3.15; >= 3.4.0, < 3.4.10; >= 3.5.0, < 3.5.4; >= 3.6.0-rc1, <= 3.6.0-rc1; fixed in 3.5.4, 3.3.15, 3.6.0-rc2, 3.4.10
- Go github.com/argoproj/argo-cd: affected every version

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd/v3: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3, github.com/argoproj/argo-cd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6701 (OSV record GO-2026-6701 lists affected ranges: Go github.com/argoproj/argo-cd >=0; Go github.com/argoproj/argo-cd/v2 >=2.11.0; Go github.com/argoproj/argo-cd/v3 >=3.0.0 =3.4.0 =3.5.0 =3.6.0-rc1 <3.6.0-rc2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-j6cw-g6p4-7hch (OSV record GHSA-j6cw-g6p4-7hch lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.11.0 =3.0.0 =3.4.0 =3.5.0 =3.6.0-rc1 <3.6.0-rc2 (fixed))
- Verified: https://github.com/advisories/GHSA-j6cw-g6p4-7hch (GitHub-reviewed advisory GHSA-j6cw-g6p4-7hch lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.11.0 =3.0.0 =3.4.0 =3.5.0 =3.6.0-rc1 <=3.6.0-rc1)

Commands are suggestions: review each one before running it.

Loading voting…