What is the CVSS score of CVE-2026-45807?

CVE-2026-45807 has a CVSS 3.1 base score of 7.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.4%.

Which versions of Kestra are affected by CVE-2026-45807?

Kestra orchestration platform (versions prior to 1.0.43 and 1.3.19) allows authenticated users with execution privileges to read arbitrary files from the server, including system credentials, mounted…. A patch is available.

How to fix or mitigate CVE-2026-45807?

Within 24 hours: Identify and document all Kestra deployments and their current versions. Within 7 days: Restrict execution-privilege access to minimal set of users; implement filesystem access controls to limit Kestra process permissions; enable audit logging for file access and URI requests; review and rotate any credentials accessible via affected systems. Within 30 days: Apply vendor patch to upgrade to Kestra 1.0.43, 1.3.19, or later once released; conduct forensic review of audit logs for exploitation indicators.

Kestra CVE-2026-45807

EUVD-2026-39921 HIGH

Path Traversal (CWE-22)

2026-06-26 GitHub_M

Path Traversal Kestra Kestra Io

7.7

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

7.7 HIGH

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

vuln.today AI

7.7 HIGH

Network API reachable (AV:N) with simple encoded-traversal payload (AC:L), requires a low-privilege authenticated execution account (PR:L), no interaction; reads host/cross-tenant files beyond the storage authority (S:C, C:H) with no integrity or availability impact.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Jun 26, 2026 - 23:02 EUVD

Analysis Generated

Jun 26, 2026 - 21:53 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Arbitrary file read in Kestra orchestration platform (versions prior to 1.0.43 and 1.3.19) lets an authenticated user with execution privileges read any file accessible to the Kestra process via a URL-encoded path-traversal in kestra:// storage URIs. The parentTraversalGuard checks only the literal URI string, so %2E%2E bypasses it before URI.getPath() decodes it back to '..', exposing /etc/passwd, mounted secrets, and other tenants' execution outputs. No public exploit identified at time of analysis; rated CVSS 7.7 with a scope change reflecting cross-tenant and host-filesystem exposure.

Technical ContextAI

Kestra is an event-driven workflow orchestration platform that abstracts file storage behind a StorageInterface, addressing artifacts via kestra:// URIs that map onto a local storage backend. This is a classic CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') flaw rooted in inconsistent canonicalization: the parentTraversalGuard sanitizer inspects URI.toString() (the still-encoded form) while the downstream consumer calls URI.getPath() (the decoded form), creating a parser-differential. Because the decoded path containing '..' segments is passed to Paths.get(...) without normalization, the operating system resolves the traversal at open(2) time, escaping the intended storage root. The single affected codebase is cpe:2.3:a:kestra-io:kestra, with no platform restriction since the bug is in Java URI handling.

RemediationAI

Upgrade to a patched release: Kestra 1.0.43 for the 1.0.x branch or 1.3.19 for the 1.3.x branch (Vendor-released patch: 1.0.43 and 1.3.19), as documented in advisory GHSA-3529-p4wf-xp79 (https://github.com/kestra-io/kestra/security/advisories/GHSA-3529-p4wf-xp79). If immediate patching is not possible, reduce the authenticated attack surface by tightening RBAC so that only trusted users hold execution privileges, and isolate the Kestra process: run it under a dedicated low-privilege OS account with a minimal filesystem footprint (no readable host secrets or other tenants' data on the same mount), which limits what a successful traversal can disclose but does not close the bug. Where feasible, place the affected API endpoints behind network controls (restrict access to the execution/storage-read endpoints to trusted networks) and avoid mounting sensitive secrets into the Kestra container filesystem in favor of an external secrets manager; the trade-off is operational friction in workflows that legitimately read mounted files. These are stopgaps only - upgrading is the authoritative fix.