# CVE-2026-33466: Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write

> Attackers can write arbitrary files via path traversal in archive extraction, potentially achieving remote code execution if automatic pipeline reloading is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** BIT-logstash-2026-33466, GHSA-w3rv-2cr7-p2wh

## What is CVE-2026-33466?

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.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-33466?

1 open source package ship an affected version, including logstash. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `logstash` | Bitnami | From 8.0.0 | 8.19.14, 9.2.8, 9.3.3 |

Products: Elastic Logstash.

## How do I fix CVE-2026-33466?

Upgrade logstash to a fixed version for your release line: 8.19.14, 9.2.8 or 9.3.3.

## Is CVE-2026-33466 being exploited?

There is no known exploitation of CVE-2026-33466 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Logstash

- [CVE-2019-7612](https://insights.sbomify.com/CVE-2019-7612/): Information disclosure in Logstash (critical 9.8)
- [CVE-2023-46672](https://insights.sbomify.com/CVE-2023-46672/): Logstash Insertion of Sensitive Information into Log File (high 8.4)
- [CVE-2019-7620](https://insights.sbomify.com/CVE-2019-7620/): Denial of service in Logstash (high 7.5)
- [CVE-2015-5378](https://insights.sbomify.com/CVE-2015-5378/): Information disclosure in n/a (high 7.5)
- [CVE-2016-1000221](https://insights.sbomify.com/CVE-2016-1000221/): Logstash Logs Sensitive Information (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33466 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-33466 in the wild and no public exploit code.

Affected packages and fixed versions:
- logstash (Bitnami): affected from 8.0.0; fixed in 8.19.14, 9.2.8, 9.3.3

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33466/ (Markdown: https://insights.sbomify.com/CVE-2026-33466/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33466
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33466
- OSV: https://osv.dev/vulnerability/CVE-2026-33466

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33466/
Summaries are generated and may contain mistakes; the official description above is the record.