CVE-2022-31036Network attack vector

Authenticated YAML disclosure via unchecked Helm symlinks

Published Jun 27, 2022 · Updated Apr 23, 2025

Symlink following in the Argo CD repo-server allows remote authenticated users to read out-of-repository YAML files through Helm applications. populateHelmAppDetails joined values.yaml to the application path, and loadFileIntoIfExists followed that path without verifying that the resolved target remained under the repository root. Exploitation requires repository write access, a Helm-type Application, and a symlink targeting a valid YAML file; disclosed data can include other manifests or mounted secrets.

CVSS severity4.3
Medium
EPSS probability0.87%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Symlink following in the Argo CD repo-server allows remote authenticated users to read out-of-repository YAML files through Helm applications. populateHelmAppDetails joined values.yaml to the application path, and loadFileIntoIfExists followed that path without verifying that the resolved target remained under the repository root. Exploitation requires repository write access, a Helm-type Application, and a symlink targeting a valid YAML file; disclosed data can include other manifests or mounted secrets.

The record

CVE
CVE-2022-31036
Published
Jun 27, 2022
Updated
Apr 23, 2025
Vendor
Argo Project
Product
Argo CD
Classifications
CWE-61, CWE-20, T1005
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 27, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.3.0, < 2.1.16
  2. Affected versionversion=>= 2.2.0, < 2.2.10
  3. Affected versionversion=>= 2.3.0, < 2.3.5
  4. Affected versionversion=>= 2.4.0, < 2.4.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Argo Project · Argo CDversion=>= 1.3.0, < 2.1.16; version=>= 2.2.0, < 2.2.10; version=>= 2.3.0, < 2.3.5; version=>= 2.4.0, < 2.4.1

Published CVSS scores

4.3GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0NIST NVDAV:N/AC:L/Au:S/C:P/I:N/A:N
4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-61UNIX Symbolic Link (Symlink) Following
CWE-20Improper Input Validation
T1005Data from Local System

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo