Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1

The Argo CD web terminal session does not handle the revocation of user permissions properly

CVE-2024-41666GHSA-v8wx-v5jq-qhhw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/argoproj/argo-cd/v2 2.11.7, 2.10.16, 2.9.21), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-41666: 0.69% estimated exploitation activity in the next 30 days; percentile 52.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Argo CD v2.11.3 and before, discovering that even if the user's 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 , 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 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-v8wx-v5jq-qhhw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-41666

Advisory: The Argo CD web terminal session does not handle the revocation of user permissions properly
IDs: CVE-2024-41666, GHSA-v8wx-v5jq-qhhw
Record: https://patchnext.com/advisories/cve-2024-41666 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd/v2 2.11.7, 2.10.16, 2.9.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.6.0, < 2.9.21; >= 2.10.0, < 2.10.16; >= 2.11.0, < 2.11.7; fixed in 2.11.7, 2.10.16, 2.9.21

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v8wx-v5jq-qhhw (GitHub-reviewed advisory GHSA-v8wx-v5jq-qhhw lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.6.0 =2.10.0 =2.11.0 <2.11.7)

Commands are suggestions: review each one before running it.

Loading voting…