NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

The Argo CD web terminal session does not handle the revocation of user permissions properlyGHSA-v8wx-v5jq-qhhw

MEDIUMFix: argoproj/argo-cd@05edb2a

GHSA-v8wx-v5jq-qhhw is a medium-severity (CVSS 4.7) Improper Privilege Management vulnerability in github.com/argoproj/argo-cd/v2. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/argoproj/argo-cd/v2 — see the affected versions and patch details below.

Also known asBIT-argo-cd-2024-41666CVE-2024-41666GO-2024-3006
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v8wx-v5jq-qhhw.

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.39%0.79%1.19%0.1%0.7%May 26Sep 26Nov 26

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

3 pkgs affected
🐹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

Argo CD v2.11.3 and before, discovering that even if the user's p, role:myrole, exec, create, */*, allow permissions are revoked, the user can still send any Websocket message, which allows the user to view sensitive information. Even though they shouldn't have such access.

Description

Argo CD has a Web-based terminal that allows you to get a shell inside a running pod, just like you would with kubectl exec. However, when the administrator enables this function and grants permission to the user p, role:myrole, exec, create, */*, allow, even if the user revokes this permission, the user can still perform operations in the container, as long as the user keeps the terminal view open for a long time. CVE-2023-40025 Although the token expiration and revocation of the user are fixed, however, the fix does not address the situation of revocation of only user p, role:myrole, exec, create, */*, allow permissions, which may still lead to the leakage of sensitive information.

Patches

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

v2.11.7 v2.10.16 v2.9.21

For more information

If you have any questions or comments about this advisory:

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

Credits

This vulnerability was found & reported by Shengjie Li, Huazhong University of Science and Technology Zhi Li, Huazhong University of Science and Technology Weijie Liu, Nankai University

The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/argoproj/argo-cd/v2≥ 2.6.0&&< 2.9.212.9.21go get github.com/argoproj/argo-cd/v2@v2.9.21
🐹Gogithub.com/argoproj/argo-cd/v2≥ 2.10.0&&< 2.10.162.10.16go get github.com/argoproj/argo-cd/v2@v2.10.16
🐹Gogithub.com/argoproj/argo-cd/v2≥ 2.11.0&&< 2.11.72.11.7go get github.com/argoproj/argo-cd/v2@v2.11.7

Affected Products

1 product · 3 configurations
Application
argo cdargoproj
≥ 2.11.0 && < 2.11.7
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes…

drive.google.comNVDJan 2025

Report on github.com

github.comNVDJan 2025

Detection & mitigation playbook

Open-source dependency

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

  2. Fix

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

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

Argo CD v2.11.3 and before, discovering that even if the user's ```p, role:myrole, exec, create, */*, allow``` permissions are revoked, the user can still send any Websocket message, which allows the user to view sensitive information. Even though they shouldn't have such access. ## Description Argo CD has a Web-based terminal that allows you to get a shell inside a running pod, just like you would with kubectl exec. However, when the administrator enables this function and grants permission to the user ```p, role:myrole, exec, create, */*, allow```, even if the user revokes this permission,
O3 Security · Impact-Aware SCA

Is GHSA-v8wx-v5jq-qhhw in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
The Argo CD web terminal session does not handle the…