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.2% 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-94399 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-94399?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-94399?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-94399 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.21 |
| Elasticsearch | from 9.0.0 through 9.4.6 |
| Elasticsearch | from 9.5.0 through 9.5.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Azure Linux | 3 | rubygem-elasticsearch | no fix listed | AZL-104954 |
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 impact because an authenticated attacker with network reachability is required to induce service exhaustion, while data confidentiality and system integrity remain completely unaffected. Within Red Hat OpenShift AI, the affected Elasticsearch functionality is deployed internally within cluster services, which prevents unauthenticated remote exploitation. Furthermore, container images such as Red Hat Quay do not incorporate the vulnerable code paths and are not impacted.
Restrict network access to Elasticsearch and dependent feature server instances to trusted internal clients and authorized cluster workloads only.
Implement OpenShift NetworkPolicies or firewall rules to limit ingress traffic exclusively to verified application pods and trusted administrative networks. In addition, enforce role-based access control to restrict query execution to authorized users.
Caveat: Applying strict network filtering may disrupt legitimate application services that depend on Elasticsearch if required namespaces and endpoints are not explicitly permitted.
| 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-94399.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.