<Vulnerability name="CVE-2026-102408">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Moderate</ThreatSeverity>
    <PublicDate>2026-10-06T19:31:39</PublicDate>
    <Bugzilla id="2547111" url="https://bugzilla.redhat.com/show_bug.cgi?id=2547111" xml:lang="en:us">
elasticsearch: elasticsearch: Denial of Service via crafted regular expressions in ES|QL CHUNK function
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>4.3</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-1333</CWE>
    <Details xml:lang="en:us" source="Mitre">
Inefficient Regular Expression Complexity (CWE-1333) in Elasticsearch can lead to denial of service via Regular Expression Exponential Blowup (CAPEC-492). The ES|QL CHUNK function's recursive chunking strategy accepts a list of user-supplied regular expressions used as text-splitting separators, without validating their computational complexity or bounding their execution time. An authenticated user with read access to any text-based index can submit a specially crafted regular expression that triggers catastrophic backtracking, consuming excessive CPU on Elasticsearch worker threads and degrading query throughput for other tenants on the affected node. The cluster does not crash as a result of this issue.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in Elasticsearch. An authenticated attacker with read access to an index can cause a Denial of Service (DoS) by submitting queries containing specially crafted regular expressions to the ES|QL CHUNK function. Because the component does not properly restrict regular expression complexity or limit processing time, evaluating the pattern triggers excessive CPU consumption, significantly degrading query performance on the affected node.
    </Details>
    <Statement xml:lang="en:us">
This vulnerability is rated as having Moderate impact because exploitation requires authenticated callers possessing index query permissions and causes performance degradation rather than process termination or data compromise. Within supported deployments utilizing affected Elasticsearch engines, processing malicious text-splitting expressions can exhaust node worker threads through computational backtracking. Although node services do not crash and data integrity remains unaffected, overall search throughput across multi-tenant clusters can be diminished.
    </Statement>
    <Mitigation xml:lang="en:us">
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
    </Mitigation>
    <PackageState cpe="cpe:/a:redhat:openshift_ai">
        <ProductName>Red Hat OpenShift AI (RHOAI)</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>rhoai/odh-feature-server-rhel9</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:quay:3">
        <ProductName>Red Hat Quay 3</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>quay/quay-rhel8</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:quay:3">
        <ProductName>Red Hat Quay 3</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>quay/quay-rhel9</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-102408
https://nvd.nist.gov/vuln/detail/CVE-2026-102408
https://discuss.elastic.co/t/elasticsearch-8-19-22-9-4-8-and-9-5-5-security-update-esa-2026-189/390862
    </References>
</Vulnerability>