Pipecat: Public exposure of Pipecat’s development runner can allow unauthenticated bot session creation
Impact
Pipecat versions 0.0.98 to 1.5.9 are affected by public exposure of the development runner, allowing unauthenticated bot session creation if the operator exposes it to untrusted traffic. This can consume local resources and third-party quotas. Version 1.6.0 adds a banner and documentation but does not change endpoint behavior.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.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.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
pipecat-ai · GitHub_M
pipecat
1 range
pipecat-ai · GitHub_M
pipecat
Compare with this publisher’s ranges. This does not inspect your installation.
affected
>= 0.0.98, < 1.6.0
Other versions: unknown
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-102682View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.