CVE-2026-48129
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKestra 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKestra's inputFiles task feature does not validate file names, allowing path traversal via '../' sequences. An attacker controlling untrusted webhook or execution data can write files outside the intended task working directory to arbitrary locations on the worker filesystem.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Kestra versionCheck the installed Kestra version by querying the API endpoint /api/v1/config or reviewing the Kestra startup logs. Common locations: docker logs <container> or systemctl status kestra.Affected if The installed version is any version prior to 1.3.19, 1.2.19, 1.1.19, or 1.0.43 and falls within the 1.x release line.
-
Locate inputFiles task usageSearch Kestra flow definitions (YAML files in the repository or namespace) for tasks that reference the inputFiles feature. Use the Kestra API: GET /api/v1/flows or inspect flows in the Kestra UI under the Flows section.Affected if Any flow contains tasks that process files via the inputFiles feature using untrusted or user-supplied file names.
-
Identify webhook or external data sourcesReview flows that receive data from webhooks, triggers, or external systems. Check the flow definitions for webhook inputs, execution triggers, or API-based executions that populate inputFiles.Affected if Webhooks, external triggers, or API calls can inject file names into the inputFiles processing without sanitization.
-
Inspect task execution logs for path traversal attemptsQuery Kestra execution logs via the UI or API (GET /api/v1/executions/<id>) and examine task output. Look for '../' sequences in file path parameters or unusual file creation locations on the worker filesystem.Affected if Logs show file operations containing '../' patterns or files created outside the expected task working directory.
-
Audit worker filesystem for unexpected filesOn Kestra worker nodes, inspect the task working directory (typically /tmp/kestra or /var/tmp/kestra) and surrounding directories. Look for files written in parent directories or unexpected locations.Affected if Files exist outside the designated task working directory, indicating successful path traversal exploitation.
You are affected if you run any Kestra version prior to 1.3.19/1.2.19/1.1.19/1.0.43 and use the inputFiles feature with untrusted or user-controlled file names from webhooks or external data sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Kestra versions 1.3.19, 1.2.19, 1.1.19, or 1.0.43 which contain the patch. As a compensating control, validate and sanitize any user-controlled data used in inputFiles file names before processing.
1.0.43 (for 1.0.x), 1.1.19 (for 1.1.x), 1.2.19 (for 1.2.x), or 1.3.19 (for 1.3.x)
- Identify the currently running Kestra version from your deployment configuration or container image tag
- Determine the appropriate upgrade target based on your current version branch: if on 1.0.x upgrade to 1.0.43, if on 1.1.x upgrade to 1.1.19, if on 1.2.x upgrade to 1.2.19, if on 1.3.x upgrade to 1.3.19
- Upgrade Kestra to the selected fixed version using your existing deployment mechanism (e.g., Helm upgrade, Docker image update, or package manager)
- Verify the upgrade was successful and the Kestra UI/API is accessible
- Test that inputFiles functionality works correctly with the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data