{"answers":{"affected":"1 open source package ship an affected version, including logstash. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33466 in the wild and no public exploit code.","fix":"Upgrade logstash to a fixed version for your release line: 8.19.14, 9.2.8 or 9.3.3.","what":"CVE-2026-33466 is a high-severity path traversal vulnerability in Elastic Logstash, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33466 and fix it if it is affected.\n\nWhat it is: CVE-2026-33466 is a high-severity path traversal vulnerability in Elastic Logstash, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33466 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- logstash (Bitnami): affected from 8.0.0; fixed in 8.19.14, 9.2.8, 9.3.3\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-33466/ (Markdown: https://insights.sbomify.com/CVE-2026-33466/index.md)","id":"CVE-2026-33466","markdown":"https://insights.sbomify.com/CVE-2026-33466/index.md","name":"CVE-2026-33466","record":{"aliases":["BIT-logstash-2026-33466","GHSA-w3rv-2cr7-p2wh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Logstash data processing","requires_auth":"none","summary":"Attackers can write arbitrary files via path traversal in archive extraction, potentially achieving remote code execution if automatic pipeline reloading is enabled.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"logstash","vendor":"elastic"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Improper Limitation of a Pathname to a Restricted Directory (CWE-22) in Logstash can lead to arbitrary file write and potentially remote code execution via Relative Path Traversal (CAPEC-139). The archive extraction utilities used by Logstash do not properly validate file paths within compressed archives. An attacker who can serve a specially crafted archive to Logstash through a compromised or attacker-controlled update endpoint can write arbitrary files to the host filesystem with the privileges of the Logstash process. In certain configurations where automatic pipeline reloading is enabled, this can be escalated to remote code execution.","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":"Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write","id":"CVE-2026-33466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"Improper Verification of Cryptographic Signature in Elastic Package Registry Leading to Package Integrity Bypass","id":"CVE-2026-33467"},"packages":[{"ecosystem":"Bitnami","fixed":["8.19.14","9.2.8","9.3.3"],"introduced":["8.0.0","9.0.0","9.3.0"],"last_affected":[],"package":"logstash","purl":"pkg:bitnami/logstash","source":"BIT-logstash-2026-33466"}],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service","id":"CVE-2026-33465"},"products":["Logstash"],"published":"2026-04-08","related":[{"cvss_score":9.8,"headline":"Information disclosure in Logstash","id":"CVE-2019-7612","kev_date_added":null,"published":"2019-03-25"},{"cvss_score":8.4,"headline":"Logstash Insertion of Sensitive Information into Log File","id":"CVE-2023-46672","kev_date_added":null,"published":"2023-11-15"},{"cvss_score":7.5,"headline":"Denial of service in Logstash","id":"CVE-2019-7620","kev_date_added":null,"published":"2019-10-30"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2015-5378","kev_date_added":null,"published":"2017-06-27"},{"cvss_score":7.5,"headline":"Logstash Logs Sensitive Information","id":"CVE-2016-1000221","kev_date_added":null,"published":"2017-06-16"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2016-1000222","kev_date_added":null,"published":"2017-06-16"}],"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":"total"},"state":"PUBLISHED","updated":"2026-04-10","vendors":["Elastic"]},"summary":"Attackers can write arbitrary files via path traversal in archive extraction, potentially achieving remote code execution if automatic pipeline reloading is enabled.","url":"https://insights.sbomify.com/CVE-2026-33466/"}