CVE-2026-72640 Vulnerability Analysis & Exploit Details

CVE-2026-72640
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2026-72640 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-72640 Details

Status: Analyzed

Last updated: 🕡 03 Sep 2026, 18:54 UTC
Originally published on: 🕗 13 Aug 2026, 20:17 UTC

Time between publication and last update: 20 days

CVSS Release: version 3

CVSS3 Source

security@elastic.co

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-72640 Vulnerability Summary

CVE-2026-72640: The Elastic Cloud on Kubernetes (ECK) operator reads a list of secret references from an annotation on secrets it manages, and it accepts the namespace recorded in each reference without validating that the reference is authorized for the resource being reconciled. A user whose Kubernetes permissions are limited to their own namespace can write that annotation, trigger a reconcile, and cause the operator to use its cluster-wide secret permissions to copy the contents of a secret from any other namespace into a secret the user can read.

Assessing the Risk of CVE-2026-72640

Access Complexity Graph

The exploitability of CVE-2026-72640 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-72640

CVE-2026-72640 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-72640, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-72640, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-72640 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-72640 poses no threat to data integrity.
  • Availability: None
    CVE-2026-72640 does not impact system availability.

CVE-2026-72640 References

External References

CWE Common Weakness Enumeration

CWE-441

CAPEC Common Attack Pattern Enumeration and Classification

  • XML Routing Detour Attacks CAPEC-219 An attacker subverts an intermediate system used to process XML content and forces the intermediate to modify and/or re-route the processing of the content. XML Routing Detour Attacks are Adversary in the Middle type attacks (CAPEC-94). The attacker compromises or inserts an intermediate system in the processing of the XML message. For example, WS-Routing can be used to specify a series of nodes or intermediaries through which content is passed. If any of the intermediate nodes in this route are compromised by an attacker they could be used for a routing detour attack. From the compromised system the attacker is able to route the XML process to other nodes of their choice and modify the responses so that the normal chain of processing is unaware of the interception. This system can forward the message to an outside entity and hide the forwarding and processing from the legitimate processing systems by altering the header information.
  • Transparent Proxy Abuse CAPEC-465 A transparent proxy serves as an intermediate between the client and the internet at large. It intercepts all requests originating from the client and forwards them to the correct location. The proxy also intercepts all responses to the client and forwards these to the client. All of this is done in a manner transparent to the client.

Vulnerable Configurations

  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:-:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:-:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.8:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.12.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:2.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:elastic:elastic_cloud_on_kubernetes:3.4.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-72640: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
  • CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
  • CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
  • CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...
  • CVE-2026-78006 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_wi...