{"answers":{"affected":"2 open source packages ship an affected version, including kibana and elk. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-72674 in the wild and no public exploit code.","fix":"Upgrade kibana to a fixed version for your release line: 9.3.8 or 9.4.4.","what":"CVE-2026-72674 is a medium-severity denial of service vulnerability in Elastic Kibana, 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-72674 and fix it if it is affected.\n\nWhat it is: CVE-2026-72674 is a medium-severity denial of service vulnerability in Elastic Kibana, 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-72674 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kibana (Bitnami): affected from 9.3.0; fixed in 9.3.8, 9.4.4\n- elk (Bitnami): affected from 9.3.0; fixed in 9.3.8, 9.4.4\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-72674/ (Markdown: https://insights.sbomify.com/CVE-2026-72674/index.md)","id":"CVE-2026-72674","markdown":"https://insights.sbomify.com/CVE-2026-72674/index.md","name":"CVE-2026-72674","record":{"aliases":["BIT-elk-2026-72674","BIT-kibana-2026-72674","GHSA-jx2m-7cw3-3cf8","MINI-67r3-hq59-jm4c","MINI-grqh-pw9r-c346"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana data visualization","requires_auth":"low_privilege","summary":"Attackers can cause denial of service in Kibana by sending crafted requests to the RAG Playground, exhausting memory and processing resources.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","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-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). A user-supplied list of document fields accepted by the Kibana Playground for RAG feature was neither bounded in length nor de-duplicated before it was used to assemble the response for each matching document. A single crafted request could therefore make Kibana build a response far larger than the data it was derived from, and the resulting processing and memory pressure exhausts the resources of the Kibana instance.","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":"Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service","id":"CVE-2026-72674","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"elastic:kibana","products":["elastic:kibana"],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Missing authorization in Kibana","id":"CVE-2026-72675"},"packages":[{"ecosystem":"Bitnami","fixed":["9.3.8","9.4.4"],"introduced":["9.3.0","9.4.0"],"last_affected":[],"package":"elk","purl":"pkg:bitnami/elk","source":"BIT-elk-2026-72674"},{"ecosystem":"Bitnami","fixed":["9.3.8","9.4.4"],"introduced":["9.3.0","9.4.0"],"last_affected":[],"package":"kibana","purl":"pkg:bitnami/kibana","source":"BIT-kibana-2026-72674"}],"prev":{"headline":"Incorrect Authorization in Kibana Leading to Unauthorized Deletion of Synthetics Private Locations","id":"CVE-2026-72673"},"products":["Kibana"],"published":"2026-08-13","related":[{"cvss_score":9.8,"headline":"Kibana Arbitrary Code Execution","id":"CVE-2019-7609","kev_date_added":"2022-01-10","published":"2019-03-25"},{"cvss_score":9.9,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25015","kev_date_added":null,"published":"2025-03-05"},{"cvss_score":9.9,"headline":"Deserialization in Kibana","id":"CVE-2024-37288","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.9,"headline":"Code injection in Kibana","id":"CVE-2023-31415","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.8,"headline":"Information disclosure in Kibana","id":"CVE-2018-17245","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.8,"headline":"Code injection in Kibana","id":"CVE-2018-17246","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.1,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25014","kev_date_added":null,"published":"2025-05-06"}],"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 cause denial of service in Kibana by sending crafted requests to the RAG Playground, exhausting memory and processing resources.","url":"https://insights.sbomify.com/CVE-2026-72674/"}