CVE-2022-31036

Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server

MEDIUM

4.3

CVSS Score

Published: June 27, 2022 at 07:15 PM UTC

Updated: June 17, 2026 at 04:44 AM UTC

1 product affected across 1 vendorArgo CD

Using argo-cd by argoproj?

Get instant alerts when new vulnerabilities affect argo-cd - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM4.3

Exploit prediction

EPSS 0.9%

SSVC

No known exploit

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file. Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. If you are using a version >=v2.3.0 and do not have any Helm-type Applications you may disable the Helm config management tool as a workaround.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Argo CD · Argoprojgo

95%

v < 2.1.16v < 2.2.10v < 2.3.5v < 2.4.11.3.0 ≤ v < 2.1.62.2.9 2.3.4 2.4.0

Affected range stops below 2.1.16, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.4.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/argoproj/argo-cd/commit/04c305396458508a31d03d44afea07b1c620d7cd

x_refsource_CONFIRMMitigationThird Party Advisory

Source: [email protected]

https://github.com/argoproj/argo-cd/security/advisories/GHSA-q4w5-4gq2-98vm

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: LOW
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-20CWE-61CWE-59

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card