Path Traversal in Kestra kestra:// URI handling
CVE-2026-45807 is a path traversal vulnerability in Kestra, an open-source event-driven orchestration platform. In versions prior to 1.0.43 and 1.3.19, multiple API endpoints accept a client-supplied kestra:// URI and pass it through StorageInterface.parentTraversalGuard before reading from the local storage backend. The protection is flawed because it validates the literal URI.toString() value rather than the decoded path. As a result, URL-encoded parent directory sequences such as %2E%2E are not detected by the guard. Later in the processing flow, URI.getPath() decodes %2E%2E back to .., and the resulting path is passed to Paths.get(...) without normalization. When the file is opened, the operating system resolves the .. segments, allowing traversal outside the intended storage boundary and arbitrary file reads from the host filesystem accessible to the Kestra process.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.