Vulnerabilities

Vulnerability · CVE-2026-72636

Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130).

Published Aug 13, 2026 · catalog updated Sep 1, 2026 · Uncontrolled Recursion (CWE-674) in

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-72636. EPSS is 0.42%. Act only if a listed version of Uncontrolled Recursion (CWE-674) in is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Uncontrolled Recursion (CWE-674) in).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.42%
Remediation
Version ranges on file
Affected products
cpe elastic/elasticsearch

Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wildcard groups, evaluated against a sufficiently long name, exhausts the thread stack. Elasticsearch treats a stack overflow as an unrecoverable condition and shuts the node down, so the request terminates the affected node rather than failing gracefully.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe elastic/elasticsearch< 8.19.20
  • cpe elastic/elasticsearch< 9.4.5

How to fix CVE-2026-72636

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-72636. EPSS is 0.42%. Act only if a listed version of Uncontrolled Recursion (CWE-674) in is installed.

Which versions are affected?

Compare what you have installed with < 8.19.20, < 9.4.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-674. EPSS 0.42%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 13, 2026 · Monitored products — high

    Detected

    Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wild

  2. Sep 1, 2026 · Monitored products — high

    Updated

    Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wild

Sources

  • CVE.orgVulnerability recordCVE-2026-72636

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2026-72636

    Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wild

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 2, 2026
  • Monitored products — highNov 1, 2026