CVE-2026-56143

MEDIUMPre-NVD 4.94.9—
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-09-01. a secondary CVSS source baseline 4.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.9Exploit: None knownExposed: 0

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted request that causes excessive memory consumption, which may render the affected node unavailable.

CVSS v3
4.9
EG Score
4.9(high)
EG Risk
22(Track)
EG Risk 22/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
Severity49% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 4, 2026

Advisory Details (1)

Auto-updated Sep 1, 2026
No patch confirmed yet.
generic

Elasticsearch 8.19.20, 9.3.0 Security Update (ESA-2026-47) - Security Announcements - Discuss the Elastic Stack

https://discuss.elastic.co/t/elasticsearch-8-19-20-9-3-0-security-update-esa-2026-47/390084

Vendor Advisories for CVE-2026-56143(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 64× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:53 UTCVendor advisory
  3. 2026-09-18 18:53 UTCGHSA enrichment
  4. 2026-09-17 20:42 UTCEG score recompute
  5. 2026-09-17 20:42 UTCVendor advisory
  6. 2026-09-17 20:42 UTCGHSA enrichment
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-16 21:22 UTCEG score recompute
  9. 2026-09-16 21:22 UTCVendor advisory
  10. 2026-09-16 21:22 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 22:39 UTCEG score recompute
  14. 2026-09-15 22:39 UTCVendor advisory
  15. 2026-09-15 22:39 UTCGHSA enrichment
  16. 2026-09-15 03:11 UTCEPSS rescore
  17. 2026-09-15 00:28 UTCVendor advisory
  18. 2026-09-15 00:28 UTCGHSA enrichment
  19. 2026-09-14 02:17 UTCEG score recompute
  20. 2026-09-14 02:17 UTCVendor advisory
  21. 2026-09-14 02:17 UTCGHSA enrichment
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-13 04:06 UTCEG score recompute
  24. 2026-09-13 04:06 UTCVendor advisory
  25. 2026-09-13 04:06 UTCGHSA enrichment
Show 39 more
  1. 2026-09-12 05:55 UTCEG score recompute
  2. 2026-09-12 05:55 UTCVendor advisory
  3. 2026-09-12 05:55 UTCGHSA enrichment
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 07:44 UTCEG score recompute
  6. 2026-09-11 07:44 UTCGHSA enrichment
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-10 09:33 UTCGHSA enrichment
  9. 2026-09-09 11:19 UTCEG score recompute
  10. 2026-09-09 11:19 UTCVendor advisory
  11. 2026-09-09 11:19 UTCGHSA enrichment
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 13:08 UTCEG score recompute
  14. 2026-09-08 13:08 UTCVendor advisory
  15. 2026-09-08 13:07 UTCGHSA enrichment
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-07 14:54 UTCGHSA enrichment
  18. 2026-09-06 16:35 UTCEG score recompute
  19. 2026-09-06 16:35 UTCVendor advisory
  20. 2026-09-06 16:35 UTCGHSA enrichment
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 18:23 UTCEG score recompute
  23. 2026-09-05 18:23 UTCVendor advisory
  24. 2026-09-05 18:23 UTCGHSA enrichment
  25. 2026-09-04 20:13 UTCVendor advisory
  26. 2026-09-04 20:12 UTCGHSA enrichment
  27. 2026-09-04 16:32 UTCEG score recompute
  28. 2026-09-04 16:32 UTCVendor advisory
  29. 2026-09-04 16:31 UTCGHSA enrichment
  30. 2026-09-04 05:07 UTCEPSS rescore
  31. 2026-09-03 18:12 UTCVendor advisory
  32. 2026-09-03 18:12 UTCGHSA enrichment
  33. 2026-09-02 20:00 UTCEG score recompute
  34. 2026-09-02 20:00 UTCGHSA enrichment
  35. 2026-09-02 14:12 UTCEPSS rescore
  36. 2026-09-01 20:20 UTCEG score recompute
  37. 2026-09-01 19:46 UTCEG score recompute
  38. 2026-09-01 19:26 UTCEG score recompute
  39. 2026-09-01 19:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56143?
CVE-2026-56143 is a medium vulnerability published on September 1, 2026. Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted request that causes excessive memory consumption, which may render the affected node…
When was CVE-2026-56143 disclosed?
CVE-2026-56143 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56143 actively exploited?
CVE-2026-56143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-56143?
CVE-2026-56143 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-56143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56143, 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

Explore the affected products and dependency analysis for CVE-2026-56143

Explore →

Is Your Infrastructure Affected by CVE-2026-56143?

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

Start Free Scan →Browse All CVEs