Skip to content
Heist/ feed
Back to feed
MediumFix available

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

Type: advisorySources: OSV

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 development do

Products
pipecat-ai
Affected versions
0.0.100, 0.0.101, 0.0.102, 0.0.103, 0.0.104, 0.0.105, 0.0.106, 0.0.107, 0.0.108, 0.0.98, 0.0.99, 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0
Fixed versions
1.6.0
CVEs
CVE-2026-102682
Confirmed fixed CVEs
Not specified
Updated in this feed
30 Oct 2026, 19:14 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 15 Oct 2026, 20:22 UTC

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 development do

osv:GHSA-hqm2-cfx2-2vgh

pipecat-ai

Fixed versions: 1.6.0

Complete source record
{
  "id": "e1c891ca5c4916e0aa70d94045e73d28fff1ef2efdd73f54802759d4c094cad5",
  "url": "https://osv.dev/vulnerability/GHSA-hqm2-cfx2-2vgh",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Pipecat: Public exposure of Pipecat’s development runner can allow unauthenticated bot session creation",
    "summary": "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 development do",
    "evidence": "osv:GHSA-hqm2-cfx2-2vgh",
    "products": [
      {
        "name": {
          "value": "pipecat-ai",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "1.6.0",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": [
          {
            "value": "0.0.100",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.101",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.102",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.103",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.104",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.105",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.106",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.107",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.108",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.98",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "0.0.99",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.0.0",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.1.0",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.2.0",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.2.1",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.3.0",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.4.0",
            "evidence": "/affected/0/versions"
          },
          {
            "value": "1.5.0",
            "evidence": "/affected/0/versions"
          }
        ]
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-hqm2-cfx2-2vgh",
      "aliases": [
        "CVE-2026-102682",
        "GHSA-hqm2-cfx2-2vgh"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "0.0.98"
                },
                {
                  "fixed": "1.6.0"
                }
              ]
            }
          ],
          "package": {
            "name": "pipecat-ai",
            "purl": "pkg:pypi/pipecat-ai",
            "ecosystem": "PyPI"
          },
          "versions": [
            "0.0.100",
            "0.0.101",
            "0.0.102",
            "0.0.103",
            "0.0.104",
            "0.0.105",
            "0.0.106",
            "0.0.107",
            "0.0.108",
            "0.0.98",
            "0.0.99",
            "1.0.0",
            "1.1.0",
            "1.2.0",
            "1.2.1",
            "1.3.0",
            "1.4.0",
            "1.5.0"
          ],
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-hqm2-cfx2-2vgh/GHSA-hqm2-cfx2-2vgh.json",
            "last_known_affected_version_range": "<= 1.5.0"
          }
        }
      ],
      "modified": "2026-10-15T20:30:07.013816777Z",
      "provider": "osv",
      "references": [
        "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",
        "https://github.com/pipecat-ai/pipecat/releases/tag/v1.6.0"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-345",
          "CWE-770",
          "CWE-862"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": "2026-10-14T19:17:05Z",
        "github_reviewed_at": "2026-10-15T20:22:18Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-102682",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 336053,
  "published_at": "2026-10-15T20:22:18+00:00"
}