Pipecat: Public exposure of Pipecat’s development runner can allow unauthenticated bot session creation

Why it is Yellow

• CVSS 5.6 medium
• On your watchlist: PyPI

Affected packages

References

• https://github.com/advisories/GHSA-hqm2-cfx2-2vgh
• https://github.com/pipecat-ai/pipecat/security/advisories/GHSA-hqm2-cfx2-2vgh
• https://nvd.nist.gov/vuln/detail/CVE-2026-102682
• https://github.com/pipecat-ai/pipecat/pull/5060
• https://github.com/pipecat-ai/pipecat/commit/acaac3e49f50968f3ffb645a42ecc48d71c4e723
• https://github.com/pipecat-ai/pipecat/releases/tag/v1.6.0
• https://github.com/advisories/GHSA-hqm2-cfx2-2vgh

Original description

Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. From 0.0.98 until 1.6.0, the pipecat-ai package's built-in development runner exposes unauthenticated endpoints including /start, /daily, and /daily-dialin-webhook that can create bot sessions and Daily rooms. The runner binds to localhost by default and is intended only for local development, so exploitation requires an operator to expose it to untrusted traffic through --host 0.0.0.0, a published port, or a tunnel without access controls. An unauthenticated caller can consume local resources and third-party quotas and, depending on configuration, receive a room URL and join token. Version 1.6.0 adds a prominent development-runner banner and documentation that clarifies the unauthenticated boundary and directs production deployments to an authenticated dispatcher or managed runtime, while the endpoint behavior remains by design. This issue is fixed in version 1.6.0.