CVE-2026-44716

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
34.2%
KEV
Not listed

Published

May 15, 2026

Last Modified

June 12, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Path Traversal in Pipecat Runner `/files` Endpoint — Arbitrary File Read via `%2F`-Encoded Separator · Advisory · pipecat-ai/pipecat · GitHub

https://github.com/pipecat-ai/pipecat/security/advisories/GHSA-3363-2ph6-35wh
github_release Patch Available

v1.2.0

Patch available: pipecat-ai/pipecat v1.2.0

https://github.com/pipecat-ai/pipecat/releases/tag/v1.2.0
github_pr

fix: validate download path containment in runner

Fix merged in pipecat-ai/pipecat PR #4417 on 2026-05-04 — awaiting tagged release

https://github.com/pipecat-ai/pipecat/pull/4417
github_commit

commit 7519c26ac550 (pipecat-ai/pipecat)

Fix landed in pipecat-ai/pipecat commit 7519c26ac550 — awaiting tagged release

https://github.com/pipecat-ai/pipecat/commit/7519c26ac5508573c35fa3a9c4717b013993d129

Vendor Advisories for CVE-2026-44716(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pipecat-ai0.0.100 ... 1.1.0 (21 versions)1.2.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 21:30 UTCEG score recompute
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 09:08 UTCEG score recompute
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 21:54 UTCEG score recompute
  20. 2026-06-27 07:47 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 20:12 UTCEG score recompute
  23. 2026-06-25 18:48 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 53 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-18 04:04 UTCEG score recompute
  12. 2026-06-17 17:53 UTCEPSS rescore
  13. 2026-06-17 13:26 UTCEG score recompute
  14. 2026-06-16 22:21 UTCEG score recompute
  15. 2026-06-16 17:52 UTCEPSS rescore
  16. 2026-06-16 11:07 UTCEG score recompute
  17. 2026-06-15 23:34 UTCEG score recompute
  18. 2026-06-15 17:49 UTCEPSS rescore
  19. 2026-06-14 21:48 UTCEG score recompute
  20. 2026-06-14 10:33 UTCEG score recompute
  21. 2026-06-13 23:18 UTCEG score recompute
  22. 2026-06-13 23:00 UTCEPSS rescore
  23. 2026-06-13 01:03 UTCEG score recompute
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-12 23:12 UTCEPSS rescore
  26. 2026-06-12 13:47 UTCEG score recompute
  27. 2026-06-12 02:32 UTCEG score recompute
  28. 2026-06-11 15:17 UTCEG score recompute
  29. 2026-06-11 14:00 UTCEPSS rescore
  30. 2026-06-11 04:02 UTCEG score recompute
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 16:46 UTCEG score recompute
  33. 2026-06-10 05:32 UTCEG score recompute
  34. 2026-06-09 18:17 UTCEG score recompute
  35. 2026-06-09 07:03 UTCEG score recompute
  36. 2026-06-08 19:47 UTCEG score recompute
  37. 2026-06-08 06:47 UTCEG score recompute
  38. 2026-06-07 19:33 UTCEG score recompute
  39. 2026-06-07 08:18 UTCEG score recompute
  40. 2026-06-06 21:03 UTCEG score recompute
  41. 2026-06-06 09:48 UTCEG score recompute
  42. 2026-06-05 22:33 UTCEG score recompute
  43. 2026-06-05 11:18 UTCEG score recompute
  44. 2026-06-05 00:03 UTCEG score recompute
  45. 2026-06-04 12:18 UTCEG score recompute
  46. 2026-06-04 01:03 UTCEG score recompute
  47. 2026-06-03 13:48 UTCEG score recompute
  48. 2026-06-03 02:33 UTCEG score recompute
  49. 2026-06-02 15:18 UTCEG score recompute
  50. 2026-06-02 04:03 UTCEG score recompute
  51. 2026-06-01 16:48 UTCEG score recompute
  52. 2026-06-01 05:33 UTCEG score recompute
  53. 2026-05-24 06:19 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44716?
CVE-2026-44716 is a high vulnerability published on May 15, 2026. 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…
When was CVE-2026-44716 disclosed?
CVE-2026-44716 was first published in the National Vulnerability Database on May 15, 2026, with the most recent update on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44716 actively exploited?
CVE-2026-44716 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44716?
CVE-2026-44716 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44716?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44716, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44716

Explore →

Is Your Infrastructure Affected by CVE-2026-44716?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs