GHSA-xmg8-99r8-jc2j — v2
MEDIUMGHSA-xmg8-99r8-jc2j 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.
Login screen allows message spoofing if SSO is enabled
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 GHSA-xmg8-99r8-jc2j.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-xmg8-99r8-jc2j plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cdReal-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
<!-- Use only one of the paragraphs below. Remove all others. --> <!-- For Argo CD -->- Open an issue in the Argo CD issue tracker or discussions
- Join us on Slack in channel #argo-cd
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.3.0&&< 2.3.4 | 2.3.4go 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.9go 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.15go get github.com/argoproj/argo-cd/v2@v2.1.15 |
| 🐹Go | github.com/argoproj/argo-cd | all versions | 2.1.15go get github.com/argoproj/argo-cd@v2.1.15 |
Detection & mitigation playbook
Open-source dependencyDetect
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 GHSA-xmg8-99r8-jc2j 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xmg8-99r8-jc2j can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xmg8-99r8-jc2j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| 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
Is GHSA-xmg8-99r8-jc2j in your dependencies?
O3 Security finds GHSA-xmg8-99r8-jc2j across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.