How severe is CVE-2022-24905?

CVE-2022-24905 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-24905?

CVE-2022-24905 affects the following packages: 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 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-24905?

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

How do I detect CVE-2022-24905 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/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24905 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-24905 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24905 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-24905?

CVE-2022-24905 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th 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-24905?

CVE-2022-24905 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2022-24905 was published on May 20, 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

MEDIUM severity

CVE-2022-24905 — argo-cd

MEDIUM

CVE-2022-24905 is a medium-severity (CVSS 4.3) Improper Input Validation vulnerability in github.com/argoproj/argo-cd/v2. A fix is available for github.com/argoproj/argo-cd/v2 — see the affected versions and patch details below.

Argo CD login screen allows message spoofing if SSO is enabled

Also known asGHSA-xmg8-99r8-jc2jGO-2022-0454

Published

May 20, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% 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

4 pkgs affected

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

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

A vulnerability was found in Argo CD that allows an attacker to spoof error messages on the login screen when SSO is enabled.

In order to exploit this vulnerability, an attacker would have to trick the victim to visit a specially crafted URL which contains the message to be displayed.

As far as the research of the Argo CD team concluded, it is not possible to specify any active content (e.g. Javascript) or other HTML fragments (e.g. clickable links) in the spoofed message.

Patched versions

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

v2.3.4
v2.2.9
v2.1.15

Workarounds

No workaround available.

Mitigations

It is advised to update to an Argo CD version containing a fix for this issue (see Patched versions above).

Credits

This vulnerability was discovered by Naufal Septiadi ([email protected]) and reported to us in a responsible way.

For more information

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.3.0&&< 2.3.4	2.3.4`go get github.com/argoproj/argo-cd/v2@v2.3.4`
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.2.0&&< 2.2.9	2.2.9`go get github.com/argoproj/argo-cd/v2@v2.2.9`
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.0.0&&< 2.1.15	2.1.15`go get github.com/argoproj/argo-cd/v2@v2.1.15`
🐹Go	`github.com/argoproj/argo-cd`	all versions	2.1.15`go get github.com/argoproj/argo-cd@v2.1.15`

Affected Products

1 product · 3 configurations

Application

argo cdargoproj

≥ 2.3.0 && < 2.3.4

range

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/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-cd/v2 to 2.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24905 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 HatModerate

Product	Fixed in	Advisory
Red Hat OpenShift GitOps 1.3	`openshift-gitops-1/applicationset-rhel8:v1.3.10-1`	RHSA-2022:4671
Red Hat OpenShift GitOps 1.3	`openshift-gitops-1/applicationset-rhel8:v1.3.9-3`	RHSA-2022:4691
Red Hat OpenShift GitOps 1.4	`openshift-gitops-1/applicationset-rhel8:v1.4.7-2`	RHSA-2022:4692
Red Hat OpenShift GitOps 1.5	`openshift-gitops-1/applicationset-rhel8:v1.5.1-4`	RHSA-2022:4690

Frequently Asked Questions

### Impact A vulnerability was found in Argo CD that allows an attacker to spoof error messages on the login screen when SSO is enabled. In order to exploit this vulnerability, an attacker would have to trick the victim to visit a specially crafted URL which contains the message to be displayed. As far as the research of the Argo CD team concluded, it is not possible to specify any active content (e.g. Javascript) or other HTML fragments (e.g. clickable links) in the spoofed message. ### Patched versions A patch for this vulnerability has been released in the following Argo CD versions: