CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HMedium (6.5) in elastic elasticsearch. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-102404 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102404?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102404?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102404 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Elasticsearch | from 8.0.0 through 8.19.22 |
| Elasticsearch | from 9.0.0 through 9.4.7 |
| Elasticsearch | from 9.5.0 through 9.5.4 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Azure Linux | 3 | rubygem-elasticsearch | no fix listed | AZL-106718 |
From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.
Red Hat rates this Moderate.
This vulnerability is rated as Moderate because exploitation requires valid credentials to execute search requests and is constrained to causing a denial of service without compromising data integrity or confidentiality. In typical Red Hat deployments, access to search endpoints is confined to internal platform services and authenticated users within private networks rather than exposed publicly. While an authenticated client with query privileges can trigger an out-of-memory crash on affected nodes, the issue cannot be leveraged to gain unauthorized system access or execute arbitrary code.
Restrict network exposure by limiting access to the Elasticsearch service to trusted internal networks and authorized hosts using host-level firewalling or container network policies.
On hosts utilizing firewalld, restrict traffic on the service port (TCP port 9200) to trusted IP addresses:
firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_CIDR>
firewall-cmd --permanent --remove-port=9200/tcp
firewall-cmd --reload
In OpenShift or Kubernetes environments, apply NetworkPolicies to restrict ingress traffic to the Elasticsearch pods, permitting communication only from trusted application namespaces. Additionally, restrict query execution privileges using role-based access control so that untrusted accounts cannot execute arbitrary queries.
Caveats: Network filtering and access restrictions prevent untrusted network actors from submitting queries, but authenticated trusted accounts can still trigger the vulnerability. Reloading firewall rules or applying network policies may cause brief connection drops for active sessions.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-feature-server-rhel9 | Fix deferred | |
| Red Hat Quay 3 | quay/quay-rhel8 | Not affected | |
| Red Hat Quay 3 | quay/quay-rhel9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102404.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.