{"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-72672 in the wild and no public exploit code.","fix":"Upgrade kibana to 9.4.5 or later.","what":"CVE-2026-72672 is a high-severity missing authorization 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-72672 and fix it if it is affected.\n\nWhat it is: CVE-2026-72672 is a high-severity missing authorization 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-72672 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kibana (Bitnami): affected from 9.1.0; fixed in 9.4.5\n- elk (Bitnami): affected from 9.1.0; fixed in 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-72672/ (Markdown: https://insights.sbomify.com/CVE-2026-72672/index.md)","id":"CVE-2026-72672","markdown":"https://insights.sbomify.com/CVE-2026-72672/index.md","name":"CVE-2026-72672","record":{"aliases":["BIT-elk-2026-72672","BIT-kibana-2026-72672","GHSA-6c3r-vhrx-4vh9","MINI-4qcx-266x-7m29","MINI-hhq3-426c-5rxv","MINI-p4cc-3793-9r82","MINI-vf35-7qgv-xcjh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana security tool","requires_auth":"low_privilege","summary":"Authenticated users with Elastic Security privileges can bypass Elasticsearch index restrictions to read sensitive endpoint event data, including credentials.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Elastic Security capability that suggests existing field values while a user authors endpoint policy artifacts queries Elastic Defend event data with Kibana's internal Elasticsearch account instead of the account of the requesting user. Only Kibana feature privileges are verified, and the caller's Elasticsearch index privileges are not. An authenticated user who holds Elastic Security feature privileges but no read access to the Elastic Defend event indices can therefore retrieve field values from that data, including process command line arguments, which commonly contain tokens, credentials, connection strings, and other sensitive operational detail from protected hosts.","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":"Incorrect Authorization in Kibana Leading to Disclosure of Elastic Defend Endpoint Event Data","id":"CVE-2026-72672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"elastic:kibana","products":["elastic:kibana"],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Incorrect Authorization in Kibana Leading to Unauthorized Deletion of Synthetics Private Locations","id":"CVE-2026-72673"},"packages":[{"ecosystem":"Bitnami","fixed":["9.4.5"],"introduced":["9.1.0"],"last_affected":[],"package":"elk","purl":"pkg:bitnami/elk","source":"BIT-elk-2026-72672"},{"ecosystem":"Bitnami","fixed":["9.4.5"],"introduced":["9.1.0"],"last_affected":[],"package":"kibana","purl":"pkg:bitnami/kibana","source":"BIT-kibana-2026-72672"}],"prev":{"headline":"Missing authorization in Kibana","id":"CVE-2026-72671"},"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":"Authenticated users with Elastic Security privileges can bypass Elasticsearch index restrictions to read sensitive endpoint event data, including credentials.","url":"https://insights.sbomify.com/CVE-2026-72672/"}