{"answers":{"affected":"1 open source package ship an affected version, including elasticsearch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-72636 in the wild and no public exploit code.","fix":"Upgrade elasticsearch to a fixed version for your release line: 8.19.20 or 9.4.5.","what":"CVE-2026-72636 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72636 and fix it if it is affected.\n\nWhat it is: CVE-2026-72636 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72636 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- elasticsearch (Bitnami): affected from 8.0.0; fixed in 8.19.20, 9.4.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72636/ (Markdown: https://insights.sbomify.com/CVE-2026-72636/index.md)","id":"CVE-2026-72636","markdown":"https://insights.sbomify.com/CVE-2026-72636/index.md","name":"CVE-2026-72636","record":{"aliases":["BIT-elasticsearch-2026-72636","CLEANSTART-2026-EG30881","CLEANSTART-2026-ZW02426","GHSA-mmpx-jcfp-p3wg","MINI-2jh4-77g6-qpm4","MINI-2qgp-7v3g-cpvm","MINI-3p72-p2jm-5px2","MINI-4rp8-xxjf-r2fh","MINI-597r-pv85-227v","MINI-5rgm-3jqg-h459","MINI-7hv3-fcr7-2qj6","MINI-85jc-vpjr-4rwf","MINI-87p6-fr54-h966","MINI-97fg-225h-g3c2","MINI-fgw6-96wq-67r9","MINI-fx95-vwhr-92h9","MINI-g9hx-vq43-rg3h","MINI-jwm3-8c3r-rpp2","MINI-m542-7gr5-7452","MINI-pmf6-6wv5-q3hm","MINI-pv32-hx6f-f9m6","MINI-q8m6-9mwj-c6r7","MINI-rqhc-w7cf-3hfq","MINI-vpxw-2wcq-w4c9","MINI-wf6v-8q23-ww72","MINI-xp56-jwq8-f8vv"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elasticsearch search engine","requires_auth":"low_privilege","summary":"Attackers can crash Elasticsearch nodes by sending search requests with complex wildcard patterns that cause uncontrolled recursion and stack overflow.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elasticsearch","vendor":"elastic"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wildcard groups, evaluated against a sufficiently long name, exhausts the thread stack. Elasticsearch treats a stack overflow as an unrecoverable condition and shuts the node down, so the request terminates the affected node rather than failing gracefully.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Uncontrolled Recursion in Elasticsearch Wildcard Matching Leading to Denial of Service","id":"CVE-2026-72636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"elastic:elasticsearch","products":["elastic:elasticsearch"],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"Uncontrolled Recursion in Elasticsearch Leading to Denial of Service","id":"CVE-2026-72638"},"packages":[{"ecosystem":"Bitnami","fixed":["8.19.20","9.4.5"],"introduced":["8.0.0","9.0.0"],"last_affected":[],"package":"elasticsearch","purl":"pkg:bitnami/elasticsearch","source":"BIT-elasticsearch-2026-72636"}],"prev":{"headline":"Incorrect Authorization in Kibana Leading to Unauthorized Disabling of Privilege Monitoring","id":"CVE-2026-72633"},"products":["Elasticsearch"],"published":"2026-08-13","related":[{"cvss_score":9.8,"headline":"Elasticsearch Groovy Scripting Engine Remote Code Execution","id":"CVE-2015-1427","kev_date_added":"2022-03-25","published":"2015-02-17"},{"cvss_score":8.1,"headline":"Elasticsearch Remote Code Execution","id":"CVE-2014-3120","kev_date_added":"2022-03-25","published":"2014-07-28"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2015-5377","kev_date_added":null,"published":"2018-03-06"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution","id":"CVE-2026-72649","kev_date_added":null,"published":"2026-09-01"},{"cvss_score":8.8,"headline":"Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process","id":"CVE-2026-72642","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.8,"headline":"Privilege Escalation Flaw in Elasticsearch","id":"CVE-2020-7014","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":8.8,"headline":"Improper Privilege Management in Elasticsearch","id":"CVE-2020-7009","kev_date_added":null,"published":"2020-03-31"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Elastic"]},"summary":"Attackers can crash Elasticsearch nodes by sending search requests with complex wildcard patterns that cause uncontrolled recursion and stack overflow.","url":"https://insights.sbomify.com/CVE-2026-72636/"}