Is CVE-2026-102682 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-102682 being exploited in the wild.

How severe is CVE-2026-102682?

Medium severity, with a CVSS score of 5.6, published 14 October 2026.

Which products and versions are affected?

Pipecat before 1.6.0; pipecat-ai (PyPI) >= 0.0.98, <= 1.5.0, ECOSYSTEM:introduced=0.0.98,fixed=1.6.0.

How is CVE-2026-102682 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-102682?

Check whether you run Pipecat or pipecat-ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102682: Pipecat development runner unauthenticated session creation

Q: Is there a fix for CVE-2026-102682?

Yes. pipecat-ai (PyPI): upgrade to 1.6.0 or later. Until then: Do not expose the development runner to untrusted networks. Keep it bound to localhost by default, do not set --host 0.0.0.0, avoid publishing its port, and do not tunnel it without access controls. For production use, deploy an authenticated dispatcher or managed runtime instead of the development runner. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-102682 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-102682?

Check whether you run Pipecat or pipecat-ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102682 · Severity: medium · CVSS 5.6 · Published 2026-10-14

Pipecat's development runner is designed for local-only use but can be accidentally exposed to untrusted networks if operators change its listening address or publish its port. When exposed, attackers can create bot sessions and Daily video rooms without authentication, potentially consuming quotas and resources. This is a design limitation of the development tool rather than a security flaw, and exploitation requires deliberate misconfiguration by the operator.

Technologies: pipecat-ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-102682 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-102682 being exploited in the wild.
How severe is CVE-2026-102682?: Medium severity, with a CVSS score of 5.6, published 14 October 2026.
Which products and versions are affected?: Pipecat before 1.6.0; pipecat-ai (PyPI) >= 0.0.98, <= 1.5.0, ECOSYSTEM:introduced=0.0.98,fixed=1.6.0.
Is there a fix for CVE-2026-102682?: Yes. pipecat-ai (PyPI): upgrade to 1.6.0 or later. Until then: Do not expose the development runner to untrusted networks. Keep it bound to localhost by default, do not set --host 0.0.0.0, avoid publishing its port, and do not tunnel it without access controls. For production use, deploy an authenticated dispatcher or managed runtime instead of the development runner. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102682 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-102682?: Check whether you run Pipecat or pipecat-ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pipecat-ai (PyPI): upgrade to 1.6.0 or later
```
pip install "pipecat-ai>=1.6.0"
```

Do not expose the development runner to untrusted networks. Keep it bound to localhost by default, do not set --host 0.0.0.0, avoid publishing its port, and do not tunnel it without access controls. For production use, deploy an authenticated dispatcher or managed runtime instead of the development runner.

Technical details

The development runner intentionally lacks authentication on endpoints like /start, /daily, and /daily-dialin-webhook to support local development workflows. If an operator binds it to 0.0.0.0, exposes it via port forwarding, or tunnels it without access controls, unauthenticated callers can invoke these endpoints to create bot sessions and consume third-party service quotas. The advisory is primarily a clarification of the security boundary; Pipecat 1.6.0 adds documentation and startup warnings rather than architectural changes.

Affected products

Pipecat Pipecat before 1.6.0

Identifiers

CVE-2026-102682
GHSA-hqm2-cfx2-2vgh

Timeline

2026-10-15: disclosed
2026: patched: Pipecat 1.6.0 adds documentation and warning banner; no architectural fix applied

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.