How severe is CVE-2022-31034?

CVE-2022-31034 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31034?

CVE-2022-31034 affects the following packages: github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-31034?

Update github.com/argoproj/argo-cd to 2.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31034 is resolved across your whole dependency graph.

How do I detect CVE-2022-31034 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-31034 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-31034 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31034 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-31034?

CVE-2022-31034 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-31034?

CVE-2022-31034 is classified as Insufficient Random Values (CWE-330), CWE-331 (CWE-331), CWE-335 (CWE-335). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-31034 published, and has it been updated?

CVE-2022-31034 was published on June 27, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-31034 — argo-cd

HIGHFix: argoproj/argo-cd@17f7f4f

CVE-2022-31034 is a high-severity (CVSS 8.3) Insufficient Random Values vulnerability in github.com/argoproj/argo-cd. A fix is available for github.com/argoproj/argo-cd — see the affected versions and patch details below.

Insecure entropy in argo-cd

Also known asGHSA-2m7h-86qq-fp4vGO-2022-0497

Published

Jun 27, 2022

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31034.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

🐹github.com/argoproj/argo-cd🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. (The specific weak parameters are listed in the References section.)

The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact (potentially granting an attacker admin access to Argo CD). The CVSS for this Security Advisory assumes the worst-case scenario.

Patches

A patch for this vulnerability has been released in the following Argo CD versions:

v2.4.1
v2.3.5
v2.2.10
v2.1.16

Workarounds

There are no workarounds. You must upgrade to a patched version to resolve the vulnerability.

References

These are the insufficiently-random parameters:

(since 0.11.0) The state parameter generated by the argocd login command for Oauth2 login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide the entropy required in the spec. This parameter is a "recommended" part of the Oauth2 flow and helps protect against cross-site request forgery attacks.
(since 1.7.2, when PKCE was added) The code_verifier parameter generated by the argocd login command for Oauth2+PKCE login used a non-cryptographically secure source of entropy. The attacks mitigated by PKCE are complex but have been observed in the wild.
(since 0.11.0) The state parameter generated by the Argo CD API server during a UI-initiated Oauth2 login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide the entropy required in the spec. This parameter is a "recommended" part of the Oauth2 flow and helps protect against cross-site request forgery attacks.
(since 0.11.0) The nonce parameter generated by the Argo CD API server during a UI-initiated Oauth2 implicit flow login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide sufficient entropy. This parameter is a required part of the OIDC implicit login flow and helps protect against replay attacks.

Credits

Originally discovered by @jgwest. @jannfis and @crenshaw-dev re-discovered the vulnerability when reviewing notes from ADA Logics' security audit of the Argo project sponsored by CNCF and facilitated by OSTIF. Thanks to Adam Korczynski and David Korczynski for their work on the audit.

For more information

Open an issue in the Argo CD issue tracker or discussions
Join us on Slack in channel #argo-cd

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd`	≥ 0.11.0&&< 2.1.16	2.1.16`go get github.com/argoproj/argo-cd@v2.1.16`
🐹Go	`github.com/argoproj/argo-cd/v2`	all versions	2.1.16`go get github.com/argoproj/argo-cd/v2@v2.1.16`
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.2.0&&< 2.2.10	2.2.10`go get github.com/argoproj/argo-cd/v2@v2.2.10`
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.3.0&&< 2.3.5	2.3.5`go get github.com/argoproj/argo-cd/v2@v2.3.5`
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.4.0&&< 2.4.1	2.4.1`go get github.com/argoproj/argo-cd/v2@v2.4.1`

Affected Products

1 product · 4 configurations

Application

argo cdargoproj

≥ 0.11.0 && < 2.1.16

3 versions

2.2.92.3.42.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-cd to 2.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31034 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenShift GitOps 1.3	`openshift-gitops-1/argocd-rhel8:v1.3.12-1`	RHSA-2022:5187
Red Hat OpenShift GitOps 1.3	`openshift-gitops-1/argocd-rhel8:v1.3.11-4`	RHSA-2022:5192
Red Hat OpenShift GitOps 1.4	`openshift-gitops-1/argocd-rhel8:v1.4.9-3`	RHSA-2022:5153
Red Hat OpenShift GitOps 1.5	`openshift-gitops-1/argocd-rhel8:v1.5.3-2`	RHSA-2022:5152

Frequently Asked Questions

### Impact All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. (The specific weak parameters