Vulnerability in pipecat-ai (CVE-2026-102682)
Summary
Vulnerability in pipecat-ai (CVE-2026-102682). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.6.0 or later.
Original description
The description as published by the source.
Pipecat’s built-in development runner exposes endpoints that create bot sessions and, for the Daily transport, paid Daily rooms. These development endpoints intentionally do not authenticate callers.
The runner binds to localhost by default and is designed exclusively for local development. It is not built or supported as a production server. Exploitation therefore requires an operator to deliberately make the development runner reachable from an untrusted network, such as by setting --host 0.0.0.0, publishing its port, or using a public tunnel without access controls.
If exposed in this way, an unauthenticated caller may invoke endpoints including /start, /daily, and /daily-dialin-webhook. Depending on the endpoint and configuration, this can create a bot session or Daily room and may return a room URL and join token. Repeated requests may also consume local resources and third-party service quotas.
The consequences of interacting with a launched bot depend on that bot’s configuration and connected tools. Access to external systems or sensitive information is not an inherent capability of the development runner and is therefore not included as a general impact.
Pipecat 1.6.0 clarifies this security boundary in two ways:
- The development runner displays a prominent startup banner identifying it as a development tool.
- The documentation explicitly states that the runner must not be used as a production server or exposed directly to untrusted traffic.
The local developm…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102682 has been found in pipecat-ai.
Risk of unauthorized operations or information disclosure. CVSS score: 5.6/10.
What to do: upgrade pipecat-ai to 1.6.0 or later.
If unsure, ask your IT team or search "pipecat-ai CVE-2026-102682" on the vendor's site.
CVE-2026-102682 (pipecat-ai) — CWE-345 / CVSS v3 5.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.6.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in pipecat-ai.
Check the vendor advisory for the affected versions of pipecat-ai.
Severity: Medium (CVSS 5.6/10). Risk of unauthorized operations or information disclosure.
Update to 1.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pipecat-ai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pipecat-ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pipecat-aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pipecat-ai to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com