Pipecat: Path Traversal in Pipecat Runner `/files` Endpoint — Arbitrary File Read via `%2F`-Encoded Separator
Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. From version 0.0.90 to before version 1.2.0, a path traversal vulnerability exists in Pipecat's development runner (src/pipecat/runner/run.py). When the runner is started with the --folder flag, it exposes a GET /files/{filename:path} download endpoint. The filename path parameter is concatenated directly onto args.folder with no containment check. Starlette normalises literal ../ sequences in URLs, but %2F-encoded slashes bypass this normalisation: the path parameter is URL-decoded after routing, so ..%2F..%2Fetc%2Fpasswd resolves to a path two levels above args.folder. An attacker with network access to the runner can read any file the pipecat process has permission to access — including SSH private keys, credentials, and system files — with a single unauthenticated HTTP request. This issue has been patched in version 1.2.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-44716
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 15:00 UTC · Revision 1
Source evidence
Pipecat: Path Traversal in Pipecat Runner `/files` Endpoint — Arbitrary File Read via `%2F`-Encoded Separator
core-osv · Original sourcePublished 9 Jun 2026, 23:07 UTC
Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. From version 0.0.90 to before version 1.2.0, a path traversal vulnerability exists in Pipecat's development runner (src/pipecat/runner/run.py). When the runner is started with the --folder flag, it exposes a GET /files/{filename:path} download endpoint. The filename path parameter is concatenated directly onto args.folder with no containment check. Starlette normalises literal ../ sequences in URLs, but %2F-encoded slashes bypass this normalisation: the path parameter is URL-decoded after routing, so ..%2F..%2Fetc%2Fpasswd resolves to a path two levels above args.folder. An attacker with network access to the runner can read any file the pipecat process has permission to access — including SSH private keys, credentials, and system files — with a single unauthenticated HTTP request. This issue has been patched in version 1.2.0.
osv:CVE-2026-44716
Complete source record
{
"id": "15f2552e39672653333ac5268f950803b88ec02a7315e9f4db6aa2bb9980a686",
"url": "https://osv.dev/vulnerability/CVE-2026-44716",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Pipecat: Path Traversal in Pipecat Runner `/files` Endpoint — Arbitrary File Read via `%2F`-Encoded Separator",
"summary": "Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. From version 0.0.90 to before version 1.2.0, a path traversal vulnerability exists in Pipecat's development runner (src/pipecat/runner/run.py). When the runner is started with the --folder flag, it exposes a GET /files/{filename:path} download endpoint. The filename path parameter is concatenated directly onto args.folder with no containment check. Starlette normalises literal ../ sequences in URLs, but %2F-encoded slashes bypass this normalisation: the path parameter is URL-decoded after routing, so ..%2F..%2Fetc%2Fpasswd resolves to a path two levels above args.folder. An attacker with network access to the runner can read any file the pipecat process has permission to access — including SSH private keys, credentials, and system files — with a single unauthenticated HTTP request. This issue has been patched in version 1.2.0.",
"evidence": "osv:CVE-2026-44716",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-44716",
"aliases": [
"CVE-2026-44716",
"GHSA-3363-2ph6-35wh",
"PYSEC-2026-2877"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/pipecat-ai/pipecat",
"type": "GIT",
"events": [
{
"introduced": "fdaa4e476ef4881c10c71228fab36185ddf10ba2"
},
{
"fixed": "ea296babe948f2e6c13489770ef38f23948558b3"
},
{
"fixed": "7519c26ac5508573c35fa3a9c4717b013993d129"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:pipecat:pipecat:*:*:*:*:*:python:*:*",
"range": [
{
"introduced": "0.0.90"
},
{
"fixed": "1.2.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "7519c26ac5508573c35fa3a9c4717b013993d129"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "ea296babe948f2e6c13489770ef38f23948558b3"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v1.2.0"
}
]
}
}
],
"versions": [
"v1.1.0",
"v1.0.0",
"v0.0.108",
"v0.0.95",
"v0.0.107",
"v0.0.106",
"v0.0.105",
"v0.0.104",
"v0.0.103",
"v0.0.102",
"v0.0.101",
"v0.0.100",
"v0.0.99",
"v0.0.98",
"v0.0.97",
"v0.0.96",
"v0.0.94",
"v0.0.93",
"v0.0.92",
"v0.0.91",
"v0.0.90"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44716.json"
}
}
],
"modified": "2026-10-28T02:30:51.148930923Z",
"provider": "osv",
"references": [
"https://github.com/pipecat-ai/pipecat/releases/tag/v1.2.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44716.json",
"https://github.com/pipecat-ai/pipecat/security/advisories/GHSA-3363-2ph6-35wh",
"https://nvd.nist.gov/vuln/detail/CVE-2026-44716",
"https://github.com/pipecat-ai/pipecat/commit/7519c26ac5508573c35fa3a9c4717b013993d129",
"https://github.com/pipecat-ai/pipecat/pull/4417"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44716.json"
}
},
"related_cves": [
{
"value": "CVE-2026-44716",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 519705,
"published_at": "2026-06-09T23:07:25.868+00:00"
}