# CVE-2026-45807: Kestra: Path traversal via URL-encoded "%2E%2E" in execution and namespace file endpoints allows arbitrary file read

> An authenticated user can read arbitrary files on the host filesystem via URL-encoded path traversal in Kestra API endpoints.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-3529-p4wf-xp79

## What is CVE-2026-45807?

CVE-2026-45807 is a high-severity path traversal vulnerability in kestra-io kestra, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.43 and 1.3.19, several Kestra API endpoints accept a kestra:// URI from the client and pass it through StorageInterface.parentTraversalGuard before reading the underlying file from the local storage backend. The guard only inspects the literal URI.toString(), so a URL-encoded .. written as %2E%2E slips through. The downstream code then calls URI.getPath(), which decodes %2E%2E back to .., and the resulting path is handed to Paths.get(...) without normalization. The OS resolves the .. segments at open(2) time, so an authenticated user with a single execution can read any file the Kestra process has access to on the host filesystem (/etc/passwd, mounted secrets, other tenants' execution outputs, etc.). This vulnerability is fixed in 1.0.43 and 1.3.19.

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

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

It affects 1 product.


Products: Kestra Kestra.

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

No fix has been published for CVE-2026-45807 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45807 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45807 exists.

## Other vulnerabilities in kestra-io kestra

- [CVE-2026-49869](https://insights.sbomify.com/CVE-2026-49869/): Kestra OSS OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2026-53576](https://insights.sbomify.com/CVE-2026-53576/): Kestra: Unauthenticated RCE via /configs path-suffix auth-filter bypass (critical 10.0)
- [CVE-2026-34612](https://insights.sbomify.com/CVE-2026-34612/): Kestra: Remote Code Execution via SQL Injection (critical 10.0)
- [CVE-2026-38428](https://insights.sbomify.com/CVE-2026-38428/): SQL injection in n/a (critical 9.8)
- [CVE-2026-55069](https://insights.sbomify.com/CVE-2026-55069/): Kestra BasicAuth Password Stored as SHA-512 Enables Offline Brute-Force Attack (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45807 is a high-severity path traversal vulnerability in kestra-io kestra, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45807 exists.

Affected product: kestra-io kestra. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-45807/ (Markdown: https://insights.sbomify.com/CVE-2026-45807/index.md)
```

## Sources

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

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