CVE-2023-31419

HIGHNVD 6.57.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.9 because EPSS predicts 61% probability of exploitation within the next 30 days (top 0.9% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
7.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 61%
CISA-KEV: Not listedEPSS PROB: 61%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service.

CVSS v3
6.5
EG Score
7.9(high)
EG Risk
64(Track)
EG Risk 64/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity79% × 45%
Exploitation61% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
61%
EPSS %ILE
99%
KEV
Not listed

Published

October 26, 2023

Last Modified

February 13, 2025

References (6)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.elasticsearch:elasticsearch8.0.0 ... 8.9.0 (31 versions)8.9.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:52 UTCEPSS rescore
  2. 2026-07-26 14:52 UTCEPSS rescore
  3. 2026-07-25 14:16 UTCEPSS rescore
  4. 2026-07-24 14:15 UTCEPSS rescore
  5. 2026-07-23 14:16 UTCEPSS rescore
  6. 2026-07-23 14:16 UTCEPSS rescore
  7. 2026-07-23 02:22 UTCEG score recompute▲ 1.40
  8. 2026-07-22 23:09 UTCEG score recompute
  9. 2026-07-22 14:06 UTCEPSS rescore
  10. 2026-07-22 14:06 UTCEPSS rescore
  11. 2026-07-20 17:06 UTCEPSS rescore
  12. 2026-07-19 14:29 UTCEPSS rescore
  13. 2026-07-19 14:29 UTCEPSS rescore
  14. 2026-07-18 10:03 UTCEPSS rescore
  15. 2026-07-18 10:03 UTCEPSS rescore
  16. 2026-07-16 17:01 UTCEPSS rescore
  17. 2026-07-16 17:01 UTCEPSS rescore
  18. 2026-07-15 16:56 UTCEPSS rescore
  19. 2026-07-15 16:56 UTCEPSS rescore
  20. 2026-07-15 05:49 UTCOSV refresh
  21. 2026-07-13 22:28 UTCEPSS rescore
  22. 2026-07-13 22:28 UTCEPSS rescore
  23. 2026-07-13 06:11 UTCEPSS rescore
  24. 2026-07-13 06:11 UTCEPSS rescore
  25. 2026-07-12 05:45 UTCEPSS rescore
Show 71 more
  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-06 16:26 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-05 02:28 UTCEPSS rescore
  8. 2026-07-04 06:29 UTCEPSS rescore
  9. 2026-07-02 16:59 UTCEPSS rescore
  10. 2026-07-01 15:04 UTCEPSS rescore
  11. 2026-06-30 23:21 UTCEPSS rescore
  12. 2026-06-30 23:21 UTCEPSS rescore
  13. 2026-06-29 14:05 UTCEPSS rescore
  14. 2026-06-28 14:06 UTCEPSS rescore
  15. 2026-06-28 14:06 UTCEPSS rescore
  16. 2026-06-27 06:04 UTCOSV refresh
  17. 2026-06-27 03:07 UTCEPSS rescore
  18. 2026-06-25 13:48 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-22 14:24 UTCEPSS rescore
  23. 2026-06-22 14:24 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-21 01:58 UTCEPSS rescore
  26. 2026-06-18 17:51 UTCEPSS rescore
  27. 2026-06-18 17:51 UTCEPSS rescore
  28. 2026-06-17 17:51 UTCEPSS rescore
  29. 2026-06-17 17:51 UTCEPSS rescore
  30. 2026-06-16 17:51 UTCEPSS rescore
  31. 2026-06-16 17:51 UTCEPSS rescore
  32. 2026-06-15 17:47 UTCEPSS rescore
  33. 2026-06-14 23:16 UTCEPSS rescore
  34. 2026-06-13 22:59 UTCEPSS rescore
  35. 2026-06-13 22:59 UTCEPSS rescore
  36. 2026-06-12 23:10 UTCEPSS rescore
  37. 2026-06-11 13:59 UTCEPSS rescore
  38. 2026-06-10 22:17 UTCEPSS rescore
  39. 2026-06-10 13:21 UTCEPSS rescore
  40. 2026-06-10 13:21 UTCEPSS rescore
  41. 2026-06-09 16:47 UTCOSV refresh
  42. 2026-06-07 15:23 UTCEPSS rescore
  43. 2026-06-07 15:23 UTCEPSS rescore
  44. 2026-06-06 13:46 UTCEPSS rescore
  45. 2026-06-06 13:46 UTCEPSS rescore
  46. 2026-06-05 22:46 UTCEPSS rescore
  47. 2026-06-05 22:46 UTCEPSS rescore
  48. 2026-06-05 06:09 UTCEPSS rescore
  49. 2026-06-05 06:09 UTCEPSS rescore
  50. 2026-06-04 13:11 UTCEPSS rescore
  51. 2026-06-04 13:11 UTCEPSS rescore
  52. 2026-06-02 20:12 UTCEPSS rescore
  53. 2026-06-02 20:12 UTCEPSS rescore
  54. 2026-06-02 20:12 UTCEPSS rescore
  55. 2026-06-01 13:51 UTCEPSS rescore
  56. 2026-05-31 22:29 UTCEPSS rescore
  57. 2026-05-31 22:29 UTCEPSS rescore
  58. 2026-05-31 22:29 UTCEPSS rescore
  59. 2026-05-31 00:15 UTCEPSS rescore
  60. 2026-05-31 00:15 UTCEPSS rescore
  61. 2026-05-29 13:43 UTCEPSS rescore
  62. 2026-05-28 13:43 UTCEPSS rescore
  63. 2026-05-28 13:43 UTCEPSS rescore
  64. 2026-05-27 13:39 UTCEPSS rescore
  65. 2026-05-27 13:39 UTCEPSS rescore
  66. 2026-05-26 13:43 UTCEPSS rescore
  67. 2026-05-26 13:43 UTCEPSS rescore
  68. 2026-05-26 07:18 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-26 07:17 UTCEPSS rescore
  71. 2026-05-24 15:01 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsqrtZeroKnowledge/Elasticsearch-Exploit-CVE-2023-31419
    First seen Sep 22, 2023

    Elasticsearch Stack Overflow Vulnerability

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-31419?
CVE-2023-31419 is a high vulnerability published on October 26, 2023. A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service.
When was CVE-2023-31419 disclosed?
CVE-2023-31419 was first published in the National Vulnerability Database on October 26, 2023, with the most recent update on February 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-31419 actively exploited?
CVE-2023-31419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 61% probability of exploitation in the next 30 days, which ranks it in the top 0.9% of all scored CVEs.
What is the CVSS score of CVE-2023-31419?
CVE-2023-31419 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.9.
How do I remediate CVE-2023-31419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-31419, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-31419

Explore →

Is Your Infrastructure Affected by CVE-2023-31419?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs