TinyIce: Missing authentication on WebRTC ingest endpoint allows unauthorized stream injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

EPSS

• CVE-2026-45327: 0.36% estimated exploitation activity in the next 30 days; percentile 29.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Title Missing authentication on WebRTC ingest endpoint allows unauthenticated stream injection in TinyIce Ecosystem / Package - Ecosystem: Go (or "Other" — TinyIce is shipped as a Go binary, not a Go module published to a registry) - Package name: github.com/DatanoiseTV/tinyice Affected versions (Introduced 2026-02-21 in commit e2b60d6 — "debug: add Go Live connection tracing and backend data flow logging" — when handleWebRTCSourceOffer was registered at /webrtc/source-offer without an authentication check. Every tagged release from v0.8.95 through v2.4.1 ships the vulnerable handler.) Patched versions Severity - CVSS 3.1 base score: 7.4 (High) - CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L - CWE: CWE-306: Missing Authentication for Critical Function Description TinyIce's WebRTC source-ingest HTTP endpoint, POST /webrtc/source-offer?mount=<mount, accepted any inbound WebRTC SDP offer with no authentication check. The handler routed the offer to…

Published by the source

18 May 2026, 17:20 UTC

Last modified by the source

9 Jun 2026, 11:56 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p7c4-8x34-8j8f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45327

Advisory: TinyIce: Missing authentication on WebRTC ingest endpoint allows unauthorized stream injection
IDs: CVE-2026-45327, GHSA-p7c4-8x34-8j8f
Record: https://patchnext.com/advisories/cve-2026-45327 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/DatanoiseTV/tinyice 2.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/DatanoiseTV/tinyice: affected >= 0.8.95, <= 2.4.1; fixed in 2.5.0

## Suggested inspection (read-only)
- Go github.com/DatanoiseTV/tinyice: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/DatanoiseTV/tinyice.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p7c4-8x34-8j8f (GitHub-reviewed advisory GHSA-p7c4-8x34-8j8f lists affected ranges: Go github.com/DatanoiseTV/tinyice >=0.8.95 <=2.4.1)

Commands are suggestions: review each one before running it.