CVE-2026-56144

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 5.3; sources differ by 0.0.

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

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

Incorrect Authorization (CWE-863) in Elasticsearch can allow an authenticated user with limited index privileges to exploit insufficient authorization controls in the ingest simulation feature. By targeting indices they are not authorized to access directly, the user can cause those indices' configured ingest pipelines to execute and return their output, potentially disclosing data processed or enriched by those pipelines. Additionally, the same feature can be used to retrieve index mapping metadata for indices the user are not authorized to access directly.

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

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

Elasticsearch 8.19.18, 9.3.7, 9.4.4 Security Update (ESA-2026-56) - Security Announcements - Discuss the Elastic Stack

https://discuss.elastic.co/t/elasticsearch-8-19-18-9-3-7-9-4-4-security-update-esa-2026-56/388555

Vendor Advisories for CVE-2026-56144(1)

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 17× in last 7d / 25× 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-30 16:28 UTCEPSS rescore
  2. 2026-07-30 10:15 UTCEG score recompute
  3. 2026-07-30 10:15 UTCGHSA enrichment
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-30 01:30 UTCEPSS rescore
  6. 2026-07-29 10:11 UTCEG score recompute
  7. 2026-07-29 10:11 UTCGHSA enrichment
  8. 2026-07-28 15:37 UTCEPSS rescore
  9. 2026-07-28 10:08 UTCEG score recompute
  10. 2026-07-28 10:07 UTCGHSA enrichment
  11. 2026-07-27 10:04 UTCEG score recompute
  12. 2026-07-27 10:04 UTCGHSA enrichment
  13. 2026-07-26 14:54 UTCEPSS rescore
  14. 2026-07-26 10:01 UTCEG score recompute
  15. 2026-07-26 10:01 UTCGHSA enrichment
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 03:20 UTCEG score recompute
  20. 2026-07-22 22:59 UTCEG score recompute
  21. 2026-07-22 22:59 UTCGHSA enrichment
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 21:25 UTCEG score recompute
  24. 2026-07-21 20:15 UTCEG score recompute
  25. 2026-07-21 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56144?
CVE-2026-56144 is a medium vulnerability published on July 21, 2026. Incorrect Authorization (CWE-863) in Elasticsearch can allow an authenticated user with limited index privileges to exploit insufficient authorization controls in the ingest simulation feature. By targeting indices they are not authorized to access directly, the user can cause those indices'…
When was CVE-2026-56144 disclosed?
CVE-2026-56144 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56144 actively exploited?
CVE-2026-56144 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 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-56144?
CVE-2026-56144 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-56144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56144, 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-56144

Explore →

Is Your Infrastructure Affected by CVE-2026-56144?

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

Start Free Scan →Browse All CVEs