CVE-2026-115290

validatedZero produced an exploit or a check.

GHSA-6f4f-c5j2-2rrx ↗EUVD-2026-116072 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.5dkevAttacks confirmed in the real world.
Elastic Elasticsearch >= 8.10.0, <= 8.19.23; >= 9.0.0, <= 9.4.8; >= 9.5.0, <= 9.5.5
CWE-674 Uncontrolled Recursion
ETK-2026-3384Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1.6dTTV
31mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+36h03mcheck available+38h24magent stopped
0
+12h
+24h

description

Elasticsearch is affected by an uncontrolled recursion issue that can cause a node to terminate. An unauthenticated attacker can trigger the condition when they have network access to a node's remote cluster server interface, potentially affecting multiple reachable nodes.

mitigation

Restrict the remote cluster server interface to trusted hosts and networks using firewall rules and network segmentation. Apply the applicable Elasticsearch vendor update after validating the fixed release for your supported branch.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.41%35th percentile
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 16:43Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+1.5d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-03 16:43Z
    cve_org: trigger signal, started the run
  2. 2026-11-05 06:22Z

this entry in the feed

GET /api/v1/feed/CVE-2026-115290

{
  "etk_id": "ETK-2026-3384",
  "cve_id": "CVE-2026-115290",
  "display_id": "CVE-2026-115290",
  "ghsa_id": "GHSA-6f4f-c5j2-2rrx",
  "euvd_id": "EUVD-2026-116072",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uncontrolled recursion denial of service in Elasticsearch",
  "summary": "Elasticsearch is affected by an uncontrolled recursion issue that can cause a node to terminate. An unauthenticated attacker can trigger the condition when they have network access to a node's remote cluster server interface, potentially affecting multiple reachable nodes.",
  "mitigation": "Restrict the remote cluster server interface to trusted hosts and networks using firewall rules and network segmentation. Apply the applicable Elasticsearch vendor update after validating the fixed release for your supported branch.",
  "vendor": "Elastic",
  "product": "Elasticsearch",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.10.0, <= 8.19.23",
        ">= 9.0.0, <= 9.4.8",
        ">= 9.5.0, <= 9.5.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Elasticsearch",
      "purl": null
    }
  ],
  "cwes": [
    674
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0041,
  "epss_percentile": 0.3575,
  "epss_asof": "2026-11-06",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 30.743950933333334,
  "t0_at": "2026-11-03T16:43:59.960000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-05T07:07:41.244571+00:00",
      "days": 1.5997833862384259,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T16:43:59.960000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-11-05T04:46:56+00:00",
      "days": 1.5020375,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T16:43:59.960000+00:00",
      "url": "https://github.com/googlesky/CVE-2026-115290"
    },
    "trigger_signal": {
      "at": "2026-11-03T16:43:59.960000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T16:43:59.960000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115290"
    }
  }
}

published 2026-11-03 16:59Z
last change 2026-11-07 17:09Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.