Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1

Argo CD web terminal session doesn't expire

CVE-2023-40025GHSA-c8xw-vjgf-94hr

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.8.1, 2.7.12, 2.6.14, 2.0.0-20230821201509-e047efa8f951), 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

  • Go github.com/argoproj/argo-cd/v2

    Affected
    >= 2.6.0, < 2.6.14>= 2.7.0, < 2.7.12>= 2.8.0, <= 2.8.0>= 2.0.0-20230718200744-12a5a7a70d6e, < 2.0.0-20230821201509-e047efa8f951
    Fixed in
    2.0.0-20230821201509-e047efa8f951, 2.8.1, 2.6.14, 2.7.12

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-c8xw-vjgf-94hr lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.6.0 =2.7.0 =2.8.0 =2.0.0-20230718200744-12a5a7a70d6e <2.0.0-20230821201509-e047efa8f951

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
  • CVE-2023-40025: 0.57% estimated exploitation activity in the next 30 days; percentile 47.52 (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.

Impact All versions of Argo CD starting from v2.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. Patches A patch for this vulnerability has been released in the following Argo CD version: v2.6.14 v2.7.12 v2.8.1 Workarounds The only way to completely resolve the issue is to upgrade. Mitigations Disable web-based terminal or define RBAC rules to it https://argo-cd.readthedocs.io/en/latest/operator-manual/webbasedterminal/ 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 Thank you to bean.zhang (@zhlu32 ) of HIT-IDS ChunkL Team who…

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

    Published from ghsa record GHSA-c8xw-vjgf-94hr

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-2023-40025

Advisory: Argo CD web terminal session doesn't expire
IDs: CVE-2023-40025, GHSA-c8xw-vjgf-94hr
Record: https://patchnext.com/advisories/cve-2023-40025 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.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.8.1, 2.7.12, 2.6.14, 2.0.0-20230821201509-e047efa8f951. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.6.0, < 2.6.14; >= 2.7.0, < 2.7.12; >= 2.8.0, <= 2.8.0; >= 2.0.0-20230718200744-12a5a7a70d6e, < 2.0.0-20230821201509-e047efa8f951; fixed in 2.0.0-20230821201509-e047efa8f951, 2.8.1, 2.6.14, 2.7.12

## 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-c8xw-vjgf-94hr (GitHub-reviewed advisory GHSA-c8xw-vjgf-94hr lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.6.0 =2.7.0 =2.8.0 =2.0.0-20230718200744-12a5a7a70d6e <2.0.0-20230821201509-e047efa8f951)

Commands are suggestions: review each one before running it.

Loading voting…