# CVE-2026-102682: Pipecat: Public exposure of Pipecat’s development runner can allow unauthenticated bot session creation

> Unauthenticated attackers can create bot sessions and consume resources if the development runner is exposed to untrusted networks.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hqm2-cfx2-2vgh

## What is CVE-2026-102682?

CVE-2026-102682 is a medium-severity missing authorization vulnerability in pipecat-ai pipecat, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization), CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-102682?

2 open source packages ship an affected version, including pipecat-ai.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pipecat-ai` | PyPI | From 0.0.98 | 1.6.0 |
| `pipecat-ai` | PyPI | From 0.0.98 | 1.6.0 |

## How do I fix CVE-2026-102682?

Upgrade pipecat-ai to 1.6.0 or later.

## Is CVE-2026-102682 being exploited?

There is no known exploitation of CVE-2026-102682 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102682 and fix it if it is affected.

What it is: CVE-2026-102682 is a medium-severity missing authorization vulnerability in pipecat-ai pipecat, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102682 in the wild and no public exploit code.

Affected packages and fixed versions:
- pipecat-ai (PyPI): affected from 0.0.98; fixed in 1.6.0
- pipecat-ai (PyPI): affected from 0.0.98; fixed in 1.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102682/ (Markdown: https://insights.sbomify.com/CVE-2026-102682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102682
- OSV: https://osv.dev/vulnerability/CVE-2026-102682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102682/
Summaries are generated and may contain mistakes; the official description above is the record.