ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-31418

An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer.

Published Oct 26, 2023 · catalog updated Jun 17, 2026 · An issue has been

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

Check if you run it

No confirmed exploitation is on record for CVE-2023-31418. EPSS is 2.05%. Act only if a listed version of An issue has been is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (An issue has been).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
2.05%
Remediation
Version ranges on file
Affected products
cpe elastic/elastic cloud enterprise · cpe elastic/elasticsearch

An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.

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/elastic cloud enterprise3.6.0
  • cpe elastic/elastic cloud enterprise<= 2.13.3
  • cpe elastic/elasticsearch<= 7.17.12
  • cpe elastic/elasticsearch>= 8.0.0, <= 8.8.2

How to fix CVE-2023-31418

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-2023-31418. EPSS is 2.05%. Act only if a listed version of An issue has been is installed.

Which versions are affected?

Compare what you have installed with elastic/elastic cloud enterprise 3.6.0; elastic/elastic cloud enterprise <= 2.13.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption. EPSS 2.05%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Elasticsearch security

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. Oct 26, 2023 · Monitored products — high

    Detected

    An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.

  2. Jun 17, 2026 · Monitored products — high

    Updated

    An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.

Sources

  • CVE.orgVulnerability recordCVE-2023-31418

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2023-31418

    An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 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