# CVE-2026-49984: Path traversal in kestra

> Authenticated users can read arbitrary server files, including secrets and other tenants' data, via a path traversal vulnerability in the file download API.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-qw4v-6w32-xx9h

## What is CVE-2026-49984?

CVE-2026-49984 is a high-severity path traversal vulnerability in kestra-io kestra, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.23, the local internal-storage backend validates user-supplied paths for .. traversal before it converts Windows-style backslashes to forward slashes. An attacker can therefore smuggle a traversal sequence past the guard using backslashes (..\..\..\); the guard sees a harmless string, and the path is only rewritten to ../../../ after validation, immediately before the file is opened. Any authenticated user who can view an execution (the lowest-privilege role) can call GET /api/v1/{tenant}/executions/{executionId}/file?path=… and read any file on the server filesystem readable by the Kestra process, outside the storage sandbox and across every tenant and namespace. This includes the embedded H2 database (all flows, all users, all stored secrets), internal storage of every other tenant/namespace, mounted secret files, and the process environment (/proc/self/environ) which contains configured database and secret-backend credentials. It is a complete breach of Kestra's storage isolation and multi-tenancy boundary. This vulnerability is fixed in 1.0.45 and 1.3.23.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-49984?

It affects 1 product.


Products: Kestra Kestra.

## How do I fix CVE-2026-49984?

No fix has been published for CVE-2026-49984 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49984 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49984 exists.

## Other vulnerabilities in kestra-io kestra

- [CVE-2026-49869](https://insights.sbomify.com/CVE-2026-49869/): Kestra OSS OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2026-53576](https://insights.sbomify.com/CVE-2026-53576/): Kestra: Unauthenticated RCE via /configs path-suffix auth-filter bypass (critical 10.0)
- [CVE-2026-34612](https://insights.sbomify.com/CVE-2026-34612/): Kestra: Remote Code Execution via SQL Injection (critical 10.0)
- [CVE-2026-38428](https://insights.sbomify.com/CVE-2026-38428/): SQL injection in n/a (critical 9.8)
- [CVE-2026-55069](https://insights.sbomify.com/CVE-2026-55069/): Kestra BasicAuth Password Stored as SHA-512 Enables Offline Brute-Force Attack (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49984 and fix it if it is affected.

What it is: CVE-2026-49984 is a high-severity path traversal vulnerability in kestra-io kestra, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49984 exists.

Affected product: kestra-io kestra. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49984/ (Markdown: https://insights.sbomify.com/CVE-2026-49984/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49984
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49984
- OSV: https://osv.dev/vulnerability/CVE-2026-49984

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49984/
Summaries are generated and may contain mistakes; the official description above is the record.