{"id":"CVE-2026-72645","aliases":["BIT-elasticsearch-2026-72645","EUVD-2026-58282","GHSA-vgfg-5pqm-8394"],"status":"published","title":"Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.0042,"percentile":0.3678,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-789"],"published":"2026-08-13T19:13:33Z","modified":"2026-10-28T11:12:10Z","fixes":[{"ecosystem":"Bitnami","package":"elasticsearch","fixed_in":["8.19.20","9.4.5","9.5.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"elasticsearch","ranges":[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.19.20"},{"introduced":"9.0.0"},{"fixed":"9.4.5"},{"introduced":"9.5.0"},{"fixed":"9.5.1"}]}]}],"products":[{"vendor":"elastic","product":"elasticsearch"}],"references":[{"url":"https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-9-5-1-security-update-esa-2026-116/389502","tags":["Vendor Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72645","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-vgfg-5pqm-8394"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72645.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-72645","title":"Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","status":"published","published":"2026-08-13T19:13:33.371Z","modified":"2026-08-13T20:28:53.313Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T14:19:52.016971Z"}],"euvd":[{"id":"EUVD-2026-58282","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","status":"published","published":"2026-08-13T19:13:33Z","modified":"2026-08-13T20:28:53Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T18:01:55.248337Z"}],"ghsa":[{"id":"GHSA-vgfg-5pqm-8394","title":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of...","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","status":"published","published":"2026-08-13T21:36:08Z","modified":"2026-08-13T21:36:15Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T15:10:27.325913Z"}],"nvd":[{"id":"CVE-2026-72645","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","status":"published","published":"2026-08-13T20:17:24.927Z","modified":"2026-09-01T15:31:26.297Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T14:12:37.557758Z"}],"osv":[{"id":"CVE-2026-72645","title":"Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","status":"published","published":"2026-08-13T19:13:33.371Z","modified":"2026-10-28T11:12:10.976567666Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T15:45:15.88521Z"},{"id":"BIT-elasticsearch-2026-72645","title":"Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service","description":"Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node.","status":"published","published":"2026-08-19T08:39:41.492Z","modified":"2026-09-08T08:47:15.69051305Z","updated_at":"2026-11-02T15:28:29.563843Z"}]}}