CVE-2026-63263

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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

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

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

Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Exponential Data Expansion (CAPEC-197). An authenticated user may submit a specially crafted query to the ES|QL engine that causes exponential CPU consumption during query evaluation. Because the resource exhaustion persists beyond query completion, repeated requests can fully exhaust the available query worker resources, rendering ES|QL queries unavailable until the node is restarted.

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

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (1)

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

Elasticsearch 8.19.19, 9.3.8, 9.4.4 Security Update (ESA-2026-74) - Security Announcements - Discuss the Elastic Stack

https://discuss.elastic.co/t/elasticsearch-8-19-19-9-3-8-9-4-4-security-update-esa-2026-74/388577

Vendor Advisories for CVE-2026-63263(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 / 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-27 08:40 UTCEG score recompute
  2. 2026-07-27 08:40 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 09:51 UTCEG score recompute
  6. 2026-07-26 09:51 UTCGHSA enrichment
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-24 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:22 UTCEG score recompute
  14. 2026-07-22 22:14 UTCEG score recompute
  15. 2026-07-22 22:13 UTCGHSA enrichment
  16. 2026-07-22 15:04 UTCEG score recompute
  17. 2026-07-22 15:04 UTCGHSA enrichment
  18. 2026-07-22 14:08 UTCEPSS rescore
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-22 13:33 UTCEG score recompute
  21. 2026-07-22 13:33 UTCGHSA enrichment
  22. 2026-07-22 01:44 UTCEG score recompute
  23. 2026-07-22 01:44 UTCGHSA enrichment
  24. 2026-07-21 23:34 UTCEG score recompute
  25. 2026-07-21 23:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63263?
CVE-2026-63263 is a medium vulnerability published on July 21, 2026. Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Exponential Data Expansion (CAPEC-197). An authenticated user may submit a specially crafted query to the ES|QL engine that causes exponential CPU consumption during query evaluation. Because the resource…
When was CVE-2026-63263 disclosed?
CVE-2026-63263 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-63263 actively exploited?
CVE-2026-63263 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 85.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63263?
CVE-2026-63263 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-63263?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63263, 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-63263

Explore →

Is Your Infrastructure Affected by CVE-2026-63263?

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

Start Free Scan →Browse All CVEs