# CVE-2026-45327: TinyIce: Missing authentication on WebRTC ingest endpoint allows unauthorized stream injection

> Unauthenticated attackers can inject unauthorized streams into TinyIce due to missing authentication on the WebRTC ingest endpoint.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 5 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-p7c4-8x34-8j8f, GO-2026-5534

## What is CVE-2026-45327?

CVE-2026-45327 is a high-severity missing authorization vulnerability in DatanoiseTV tinyice, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TinyIce is a streaming server for audio and video. In versions 0.8.95 through 2.4.1, missing authentication on WebRTC ingest endpoint allows unauthenticated stream injection. Version 2.5.0 fixes the issue by requiring either HTTP Basic auth or a `?password=` query parameter, comparing the supplied password against the per-mount source password (or the `default_source_password` fallback) using bcrypt, hooking into the existing brute-force IP rate-limiter (5 failed attempts per IP within 15 minutes triggers a lockout), and rejecting requests for mounts in `disabled_mounts`. The same release also tightens an adjacent endpoint, `POST /admin/golive/chunk`, which previously required session authentication but did not verify the session user's per-mount access nor check the CSRF token.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

3 open source packages ship an affected version, including github.com/DatanoiseTV/tinyice.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/DatanoiseTV/tinyice` | Go | From 0.8.95 | None |
| `github.com/DatanoiseTV/tinyice` | Go | From 0.8.95 | 2.5.0 |
| `github.com/DatanoiseTV/tinyice` | Go | From 0.8.95 | 2.5.0 |

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

Upgrade github.com/DatanoiseTV/tinyice to 2.5.0 or later.

## Is CVE-2026-45327 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45327 is a high-severity missing authorization vulnerability in DatanoiseTV tinyice, published on 5 Jun 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-45327 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/DatanoiseTV/tinyice (Go): affected from 0.8.95; no fix listed
- github.com/DatanoiseTV/tinyice (Go): affected from 0.8.95; fixed in 2.5.0
- github.com/DatanoiseTV/tinyice (Go): affected from 0.8.95; fixed in 2.5.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-45327/ (Markdown: https://insights.sbomify.com/CVE-2026-45327/index.md)
```

## Sources

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

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