Kestra: Path traversal in `LocalStorage` allows any authenticated user to read arbitrary server files via the execution file-download API (`\..\` bypasses the `..` guard)
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-49984
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:57 UTC · Revision 1
Source evidence
Kestra: Path traversal in `LocalStorage` allows any authenticated user to read arbitrary server files via the execution file-download API (`\..\` bypasses the `..` guard)
core-osv · Original sourcePublished 26 Jun 2026, 20:55 UTC
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.
osv:CVE-2026-49984
Complete source record
{
"id": "a1ba18da2e09a679336b93d6c3c9ddd111dd61b2eb15a62a159c6fe1dee9c3f9",
"url": "https://osv.dev/vulnerability/CVE-2026-49984",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Kestra: Path traversal in `LocalStorage` allows any authenticated user to read arbitrary server files via the execution file-download API (`\\..\\` bypasses the `..` guard)",
"summary": "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.",
"evidence": "osv:CVE-2026-49984",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-49984",
"aliases": [
"CVE-2026-49984",
"GHSA-qw4v-6w32-xx9h"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/kestra-io/kestra",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "670b719eb5e0fc579ad9044551223642c24335dd"
},
{
"introduced": "1e670b5e7e92f89533ee17d564263578b0d5ec8c"
},
{
"fixed": "59eb318671e81dff65e99e42438403acfa145dbe"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:kestra:kestra:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.0.45"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:kestra:kestra:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.1.0"
},
{
"fixed": "1.3.23"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v1.3.22",
"v1.3.21",
"v1.0.44",
"v1.3.20",
"v1.0.43",
"v1.3.19",
"v1.0.42",
"v1.3.18",
"v1.0.41",
"v1.3.17",
"v1.0.40",
"v1.3.16",
"v1.0.39",
"v1.3.15",
"v1.0.38",
"v1.3.14",
"v1.3.13",
"v1.0.37",
"v1.3.11",
"v1.0.36",
"v1.3.9",
"v1.0.35",
"v1.3.8",
"v1.3.7",
"v1.0.34",
"v1.3.6",
"v1.3.5",
"v1.3.4",
"v1.0.33",
"v1.3.3",
"v1.3.2",
"v1.0.32",
"v1.0.31",
"v1.3.1",
"v1.0.30",
"v1.3.0",
"v1.3.0-rc1",
"v1.0.29",
"v1.3.0-rc0",
"v1.0.28",
"v1.0.27",
"v1.0.26",
"v1.0.25",
"v1.0.24",
"v1.0.23",
"v1.0.22",
"v1.0.21",
"v1.0.20",
"v1.0.19",
"v1.0.18",
"v1.0.17",
"v1.0.16",
"v1.0.15",
"v1.0.14",
"v1.0.13",
"v1.0.12",
"v1.0.11",
"v1.0.10",
"v1.0.9",
"v1.0.8",
"v1.0.7",
"v1.0.6",
"v1.0.5",
"v1.0.4",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v0.0.1234",
"v0.19.0",
"v0.9.1",
"v0.9.0",
"v0.8.1",
"v0.8.0",
"v0.7.1",
"v0.7.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-49984.json"
}
}
],
"modified": "2026-10-28T02:30:23.173151982Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/49xxx/CVE-2026-49984.json",
"https://github.com/kestra-io/kestra/security/advisories/GHSA-qw4v-6w32-xx9h",
"https://nvd.nist.gov/vuln/detail/CVE-2026-49984"
],
"provider_metadata": {
"cwe_ids": [
"CWE-180",
"CWE-200",
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/49xxx/CVE-2026-49984.json"
}
},
"related_cves": [
{
"value": "CVE-2026-49984",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489462,
"published_at": "2026-06-26T20:55:44.344+00:00"
}