Skip to main content
No exploitation reportedFix available

CVE-2023-31418

No exploitation reported by the sources we read.

  • Published2023-10-26
  • WeaknessCWE-400

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2023-10-2618:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-31418?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-31418?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Elastic elastic cloud enterprise
BranchAffectedFixed in
2.13≤ 2.13.3no fix published
3.6= 3.6.0no fix published
Elasticsearch
BranchAffectedFixed in
7.17≤ 7.17.12no fix published
8.x≥ 8.0.0, ≤ 8.8.2no fix published
elasticsearch
BranchAffectedFixed in
8.x≥ 8.0.0, < 8.9.08.9.0
7.17< 7.17.137.17.13

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CNACVSS 3.17.5read 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-400read 2026-10-23
  • NVDweakness (CWE)CWE-400read 2026-10-23
  • FIRST EPSSEPSS score2.1 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2023-10-26
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-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.

Is CVE-2023-31418 actively exploited?

Active exploitation of CVE-2023-31418 has not been confirmed. Its EPSS score was 2.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-31418?

CVE-2023-31418 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running Elasticsearch? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database