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

CVE-2026-48129 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L. EPSS exploitation probability: 0.3%.

Is there a patch available for CVE-2026-48129?

Yes, a patch is available for CVE-2026-48129. Update the affected software to the latest version immediately.

Kestra CVE-2026-48129

Q: Which versions of Kestra are affected by CVE-2026-48129?

Path traversal in Kestra's `inputFiles` task mechanism allows remote attackers to write arbitrary files to the worker filesystem when flows forward untrusted webhook or execution data as file names.. A patch is available.

EUVD-2026-38081 MEDIUM

Path Traversal (CWE-22)

2026-06-19 GitHub_M

Path Traversal Kestra Kestra Io

6.5

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

6.5 MEDIUM

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

vuln.today AI

6.5 MEDIUM

Network-reachable via webhook (AV:N) but requires specific flow configuration forwarding untrusted input (AC:H); file write only with no read primitive confirms C:N.

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

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

Low

Lifecycle Timeline

Patch available

Jun 19, 2026 - 23:17 EUVD

Analysis Generated

Jun 19, 2026 - 20:49 vuln.today

DescriptionCVE.org

Kestra is an open-source, event-driven orchestration platform. Prior to versions 1.3.19, 1.2.19, 1.1.19, and 1.0.43, Kestra task inputFiles writes rendered file names directly under the task working directory. When a flow forwards untrusted execution or webhook data into an inputFiles file name, a caller can use ../ path segments to create or overwrite files outside that task working directory on the worker filesystem. Versions 1.3.19, 1.2.19, 1.1.19, and 1.0.43 patch the issue.

AnalysisAI

Path traversal in Kestra's inputFiles task mechanism allows remote attackers to write arbitrary files to the worker filesystem when flows forward untrusted webhook or execution data as file names. Affected across four release branches (prior to 1.3.19, 1.2.19, 1.1.19, and 1.0.43), exploitation depends on a specific flow design pattern but requires no authentication if the target webhook is publicly accessible. No public exploit code or active exploitation has been identified at time of analysis, but the CVSS integrity impact is rated High due to the ability to create or overwrite files outside the task working directory.

Technical ContextAI

Kestra (cpe:2.3:a:kestra-io:kestra) is an open-source, event-driven workflow orchestration platform that executes tasks on worker nodes. The inputFiles task feature allows flows to stage files into a task's working directory before execution, with file names rendered from flow-level data. The root cause is CWE-22 (Path Traversal): file name values derived from execution parameters or webhook payloads are written to the worker filesystem without stripping or rejecting ../ directory traversal sequences. When a Kestra flow is designed to pass externally supplied data into the inputFiles key (file name), that unsanitized string reaches the filesystem write operation, allowing traversal out of the task sandbox to arbitrary paths on the worker host. The vulnerability is architectural - it is triggered at the point where user-controlled string data crosses the trusted task working directory boundary.

RemediationAI

Upgrade Kestra to the patched release corresponding to the deployed branch: 1.3.19, 1.2.19, 1.1.19, or 1.0.43. These releases contain the vendor fix confirmed in GitHub Security Advisory GHSA-q3fw-mvgv-pjr2 (https://github.com/kestra-io/kestra/security/advisories/GHSA-q3fw-mvgv-pjr2). If an immediate upgrade is not feasible, the primary compensating control is to audit all flows using inputFiles and replace any user-controlled data in file name keys with static, hardcoded values defined by the flow developer - this eliminates the attack surface without platform-level enforcement, but requires a manual review of every affected flow. As a secondary control, restrict webhook endpoints to authenticated callers or allowlisted source IPs to reduce the network-accessible attack surface; note this does not address execution-triggered paths and may require Kestra API gateway configuration. These workarounds are flow-by-flow mitigations and do not substitute for patching.