CVE-2023-40025
MEDIUMCVE-2023-40025 is a medium-severity (CVSS 4.7) CWE-613 vulnerability in github.com/argoproj/argo-cd/v2. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2023-40025 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Argo CD web terminal session doesn't expire
Blast Radius
github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2Real-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 is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting from version 2.6.0 have a bug where open web terminal sessions do not expire. This bug allows users to send any websocket messages even if the token has already expired. The most straightforward scenario is when a user opens the terminal view and leaves it open for an extended period. This allows the user to view sensitive information even when they should have been logged out already. A patch for this vulnerability has been released in the following Argo CD versions: 2.6.14, 2.7.12 and 2.8.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.6.0&&< 2.6.14 | 2.6.14 |
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.7.0&&< 2.7.12 | 2.7.12 |
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.8.0&&< 2.8.1 | 2.8.1 |
| 🐹Go | github.com/argoproj/argo-cd/v2 | ≥ 2.0.0-20230718200744-12a5a7a70d6e&&< 2.0.0-20230821201509-e047efa8f951 | 2.0.0-20230821201509-e047efa8f951 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/argoproj/argo-cd/v2 to 2.6.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-40025 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 pinpoints whether CVE-2023-40025 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2023-40025. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-40025 in your dependencies?
O3 detects CVE-2023-40025 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.