Quick answers
- Is CVE-2026-78609 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78609 being exploited in the wild.
- How severe is CVE-2026-78609?
- Medium severity, with a CVSS score of 5.4, published 2 September 2026.
- Which products and versions are affected?
- Elastic Cloud on Kubernetes 2.6.0 through 3.4.1.
- Is there a fix for CVE-2026-78609?
- A patch was published on 2026-09-01: Fixed in version 3.5.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78609 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-78609?
- Check whether you run Elastic Cloud on Kubernetes or Elastic Cloud On Kubernetes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is an incorrect authorization flaw (CWE-863) allowing metadata spoofing (CAPEC-690). An attacker with limited Kubernetes permissions confined to a single namespace can cause attacker-controlled certificate material to be included in the Elasticsearch client trust bundle managed by ECK in a separate namespace. The vulnerability requires network access and the attacker to already hold some Kubernetes permissions within their own namespace. By injecting rogue certificates, an attacker can potentially decrypt or forge Elasticsearch client communications. The issue is resolved in ECK version 3.5.0; all versions from 2.6.0 through 3.4.1 are affected. No workarounds are available.
Affected products
- Elastic Cloud on Kubernetes 2.6.0 through 3.4.1
Timeline
- 2026-09-01: disclosed
- 2026-09-01: patched: Fixed in version 3.5.0