Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
UnratedPublic exploit

Path Traversal in Kestra kestra:// URI handling

IdentifiersCVE-2026-45807CWE-22

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

An authenticated attacker can perform arbitrary file read against the host filesystem within the privileges of the Kestra process. This can expose sensitive local files such as /etc/passwd, mounted secrets, configuration files, credentials, and other tenants' execution outputs stored on the same host. The issue breaks storage isolation and may enable follow-on compromise through disclosure of secrets or environment-specific configuration data.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the affected API endpoints to only trusted authenticated users, minimize the filesystem permissions of the Kestra process, and remove or isolate sensitive files and mounted secrets from the host context accessible to Kestra. Where feasible, disable or tightly control use of local storage backends and monitor for suspicious kestra:// URIs containing encoded traversal sequences such as %2E%2E.

Remediation

Patch, then assume compromise.

Upgrade Kestra to version 1.0.43, 1.3.19, or later, where the vulnerability is fixed. The underlying remediation should ensure traversal checks are performed on a canonicalized or normalized decoded path rather than the raw URI string, and that resolved paths are constrained to the intended storage root before file access occurs.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.