{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-49091 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49091 is a high-severity vulnerability in Elastic Kibana, published on 1 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49091 and fix it if it is affected.\n\nWhat it is: CVE-2026-49091 is a high-severity vulnerability in Elastic Kibana, published on 1 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-49091 in the wild and no public exploit code.\n\nAffected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-49091/ (Markdown: https://insights.sbomify.com/CVE-2026-49091/index.md)","id":"CVE-2026-49091","markdown":"https://insights.sbomify.com/CVE-2026-49091/index.md","name":"CVE-2026-49091","record":{"aliases":["GHSA-787j-ggjh-rhm6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana logging","requires_auth":"low_privilege","summary":"Attackers can inject control sequences into Kibana logs, altering displayed data in terminals, requiring a patch to neutralize output.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Improper Output Neutralization for Logs (CWE-117) in Kibana can lead to log injection via Log Injection-Tampering-Forging (CAPEC-93). An attacker can supply specially crafted input that is written to log files without proper neutralization. When the log files are subsequently viewed in a terminal that interprets control sequences, the injected content may alter the displayed log data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Output Neutralization for Logs in Kibana Leading to Log Injection","id":"CVE-2026-49091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"elastic:kibana","products":["elastic:kibana"],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Unintended Proxy or Intermediary ('Confused Deputy') in Kibana Leading to Unauthorized Information Exposure","id":"CVE-2026-49092"},"packages":[],"prev":{"headline":"Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service","id":"CVE-2026-49090"},"products":["Kibana"],"published":"2026-07-01","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":"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":"total"},"state":"PUBLISHED","updated":"2026-07-02","vendors":["Elastic"]},"summary":"Attackers can inject control sequences into Kibana logs, altering displayed data in terminals, requiring a patch to neutralize output.","url":"https://insights.sbomify.com/CVE-2026-49091/"}