Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-40025: Argo CD web terminal session doesn't expire

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: github.com/argoproj/argo-cd/v2 (Go) 2.0.0-20230821201509-e047efa8f951, 2.6.14, 2.7.12.
  • Severity is disputed: the assigning authority (CNA) scores it 4.7, NVD 7.1.

Low priority for now. Upgrade to github.com/argoproj/argo-cd/v2 (Go) 2.0.0-20230821201509-e047efa8f951, 2.6.14, 2.7.12 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Aug 23, 2023
Updated
Jun 17, 2026
EPSS
0.5% · 47th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.1
CNA · GitHub_M
4.7
2.4 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-40025

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for argoproj records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
argoprojargo cd

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • argoproj argo cd2.6.0 and later · up to 2.6.13 inclusive
  • argoproj argo cd2.7.11
  • argoproj argo cd2.8.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • argoproj argo-cd

    • >= 2.6.0, < 2.6.14, >= 2.7.0, < 2.7.12, = 2.8.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/argoproj/argo-cdfrom 0—
Gogithub.com/argoproj/argo-cd/v2from 2.0.0-20230718200744-12a5a7a70d6e · before 2.0.0-20230821201509-e047efa8f9512.0.0-20230821201509-e047efa8f951
Gogithub.com/argoproj/argo-cd/v2from 2.6.0 · before 2.6.142.6.14
Gogithub.com/argoproj/argo-cd/v2from 2.7.0 · before 2.7.122.7.12
Gogithub.com/argoproj/argo-cd/v2from 2.8.0 · before 2.8.12.8.1

Same product

argoproj: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-55190Argo CD: Project API Token Exposes Repository Credentials
    41Plan
  • CVE-2022-29165Argo CD will blindly trust JWT claims if anonymous access is enabled
    41Plan
  • CVE-2024-21652Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-25163Feb 8, 2023 · Argo CD leaks repository credentials in user-facing error messages and in logs
    26Monitor
  • ← EarlierCVE-2023-23947Feb 16, 2023 · Argo CD users with any cluster secret update access may update out-of-bounds cluster secrets
    34Monitor
  • Later →CVE-2023-40029Sep 7, 2023 · Cluster secret might leak in cluster details page in Argo CD
    38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/argoproj/argo-cd/v22.0.0-20230821201509-e047efa8f951Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.6.14Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.7.12Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.8.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-613 · Insufficient Session Expiration

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records