dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-41470

MEDIUM · 5.9 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

LIVE555 before 2026.04.22 has an authorization bypass in RTSP session command handling where valid Session tokens can be replayed from unauthenticated connections. Attackers who obtain a valid token can issue PLAY and TEARDOWN commands from a second TCP connection without re-authentication, causing server crashes via virtual function call errors or terminating victim sessions to disrupt active streams.

MitigationUpdate LIVE555 to version 2026.04.22 or later, which contains the fix for this authorization bypass. Additionally, implement proper session token validation on each RTSP command and consider requiring re-authentication for sensitive operations like PLAY and TEARDOWN.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if LIVE555 is running
    Check for processes named 'live555MediaServer', 'live555ProxyServer', or services listening on RTSP ports (default 554, 8554) using commands like 'ps aux | grep live' or 'netstat -an | grep -E "(554|8554)"'; also check for libraries named 'liveMedia' or 'BasicUsageEnvironment'
    Affected if LIVE555 software is present and serving RTSP traffic
  2. Determine LIVE555 version
    Run 'live555MediaServer -v' or check the binary/library version; if source is available, check the version string in the source files or git tags; compare against the fixed version 2026.04.22
    Affected if Installed version is earlier than 2026.04.22 or version cannot be determined
  3. Verify RTSP server is accessible over network
    Confirm the RTSP service is bound to a network interface (not localhost only) by examining configuration files or checking listening sockets; test connectivity with 'telnet <host> 554' or 'nc -zv <host> 554'
    Affected if RTSP service is exposed on network-accessible interfaces
  4. Confirm session authentication is in use
    Inspect RTSP server configuration or logs to determine if authentication (Digest or Basic) is required for PLAY/TEARDOWN commands; check for 'Authentication' settings in config files or examine server response headers for 'WWW-Authenticate' on unauthorized requests
    Affected if RTSP server allows PLAY or TEARDOWN commands without requiring authentication or validates session tokens only by value without binding to connection
  5. Check for replayable session tokens
    Capture RTSP traffic during a legitimate session setup (DESCRIBE, SETUP, PLAY); observe if the Session header value remains constant across different TCP connections; attempt to replay SETUP response Session ID from a new TCP connection
    Affected if Session tokens can be reused across distinct TCP connections without re-authentication

A system is affected if it runs LIVE555 versions before 2026.04.22 with an accessible RTSP server that does not bind session tokens to the originating TCP connection, allowing command replay from alternate connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update LIVE555 to version 2026.04.22 or later, which contains the fix for this authorization bypass. Additionally, implement proper session token validation on each RTSP command and consider requiring re-authentication for sensitive operations like PLAY and TEARDOWN.

Recommended fix Moderate confidence

LIVE555 version 2026.04.22 or later

  1. 1. Identify the current LIVE555 version in use by checking the library binary or build information
  2. 2. If the installed version is earlier than 2026.04.22, obtain the updated LIVE555 library version 2026.04.22 or later from the official source at download.live555.com
  3. 3. Replace the existing live555 libraries (liveMedia, BasicUsageEnvironment, groupsock,UsageEnvironment) with the updated versions
  4. 4. Rebuild any applications that link against the LIVE555 libraries
  5. 5. Restart any services or applications using the LIVE555 media server
  6. 6. Verify the RTSP server is functioning correctly by testing PLAY, PAUSE, and TEARDOWN commands

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41470 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data