Skip to content
Fencer Intel
medium 6.5

CVE-2026-103006 json

Uncontrolled Recursion in Elasticsearch Leading to Denial of Service

published last mo. modified 26d ago also BIT-elasticsearch-2026-103006 , EUVD-2026-93936

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to Denial of Service via a specially crafted, deeply nested request submitted to the aggregation feature of the search API. Elasticsearch contains an uncontrolled recursion weakness in its search aggregation processing. An authenticated user with read access to a single index can submit a specially crafted request containing deeply nested aggregation definitions. Processing this request triggers unbounded recursive execution that exhausts the server process's available resources, causing the affected node to terminate. The node does not recover automatically and requires manual intervention to restore service.

Patch / fix

  • bitnami elasticsearch 8.19.21, 9.4.6, 9.5.2
  • elasticsearch elasticsearch 8.19.21, 9.4.6, 9.5.2
  • elastic elasticsearch 8.19.21, 9.4.6, 9.5.2
  • org.elasticsearch elasticsearch 8.19.21, 9.4.6, 9.5.2

Is CVE-2026-103006 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-103006 updated cvss 6.5

elasticsearch: Elasticsearch: Denial of Service via deeply nested search aggregations

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-feature-server-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami elasticsearch
>=8.0.0, <8.19.21
>=9.0.0, <9.4.6
>=9.5.0, <9.5.2
8.19.21
9.4.6
9.5.2

Affected products

  • Elastic Elasticsearch

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.