CVE-2026-45807: Kestra path traversal (CVSS 7.7)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityNone

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected products

Kestra≥ 1.1.0 < 1.3.19 · < 1.0.43

Remediation

Fixed in

Kestra≥ 1.3.19

Patch & vendor advisories

https://github.com/kestra-io/kestra/security/advisories/GHSA-3529-p4wf-xp79

References

https://github.com/kestra-io/kestra/security/advisories/GHSA-3529-p4wf-xp79ExploitMitigationVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-45807 being actively exploited?

CVE-2026-45807 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.57%.

How severe is CVE-2026-45807?

CVE-2026-45807 has a CVSS 3.1 base score of 7.7, rated high. EPSS estimates a 0.57% probability of exploitation.

Which products are affected by CVE-2026-45807?

Affected products include Kestra.

How do I fix CVE-2026-45807?

Upgrade affected software to a fixed version, for example Kestra 1.3.19 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-45807 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo