CVE-2026-45807: Kestra: Path traversal via URL-encoded "%2E%2E" in execution and namespace file endpoints allows arbitrary file read
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kestrato a version that resolves this vulnerability.Fixed in 1.0.43 - Upgrade
Upgrade
Kestrato a version that resolves this vulnerability.Fixed in 1.3.19
Event History
Frequently Asked Questions
What is the severity of CVE-2026-45807?
CVE-2026-45807 has a severity rating of high, with a score of 7.7.
How can I mitigate the risk of CVE-2026-45807?
To mitigate CVE-2026-45807, update to Kestra version 1.0.43 or 1.3.19 or later.
What type of vulnerability is CVE-2026-45807?
CVE-2026-45807 is a Path Traversal vulnerability that allows arbitrary file reading.
Which software is affected by CVE-2026-45807?
CVE-2026-45807 affects the Kestra open-source orchestration platform.
When was CVE-2026-45807 published?
CVE-2026-45807 was published on June 26, 2026.