# CVE-2026-41470: LIVE555 < 2026.04.22 RTSP Server Authorization Bypass via Session Token

> Attackers can bypass authentication in LIVE555 RTSP servers by replaying session tokens, leading to stream disruption or server crashes.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-41470, GHSA-3x7c-xg4r-972q, UBUNTU-CVE-2026-41470, openSUSE-SU-2026:10881-1

## What is CVE-2026-41470?

CVE-2026-41470 is a high-severity authentication bypass vulnerability in LIVE555, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LIVE555 before 2026.04.22 contains an authorization bypass vulnerability in RTSP session command handling that allows attackers to replay valid Session tokens from unauthenticated connections. Attackers who obtain a valid Session token can issue PLAY and TEARDOWN commands from a second TCP connection without authentication, causing server crashes through virtual function call errors or disrupting active streams by terminating victim sessions.

Weakness: CWE-863 (Incorrect Authorization)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `live555` | openSUSE:Tumbleweed | All versions | 2026.04.22-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-41470 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41470 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41470 is a high-severity authentication bypass vulnerability in LIVE555, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41470 exists.

Affected product: LIVE555. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-41470/ (Markdown: https://insights.sbomify.com/CVE-2026-41470/index.md)
```

## Sources

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

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