Skip to main content
Mallory
UnratedVulnerability

CVE-2026-55868: SRT Encryption Downgrade via Unauthenticated Control Messages

Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-55868CWE-345

CVE-2026-55868 is an encryption-bypass vulnerability in the Secure Reliable Transport (SRT) UDP streaming library caused by insufficient authentication of encryption control messages. A keying-material request (KMREQ) that fails to install a key can move an already secured receiver into a failed encryption state, after which a cleartext data packet can be accepted and stored for playback. A remote attacker can exploit this state transition to downgrade an encrypted connection, inject arbitrary media content, or interrupt playback.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the integrity and availability of an encrypted SRT stream by allowing cleartext content to be accepted for playback. An attacker can replace stream content or disrupt the media stream. Decryption of previously encrypted traffic and arbitrary code execution are not established consequences of this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Until updates are applied, restrict SRT service exposure to trusted networks and limit incoming traffic to trusted peers where operationally feasible. Monitor for unexpected encryption-state changes, connection downgrades, and stream interruptions. These measures reduce exposure but do not correct the authentication flaw.

Remediation

Patch, then assume compromise.

Upgrade affected SRT libraries and tools to vendor-fixed packages. Debian 12 bookworm fixes are available in version 1.5.1-1+deb12u2, and Debian 13 trixie fixes are available in version 1.5.4-1+deb13u1. For Ubuntu 20.04, 22.04, 24.04, and 26.04 LTS, install the applicable updates identified by USN-8764-1, including Ubuntu Pro ESM Apps fixes where applicable.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-55868 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-55868 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-55868?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-55868.
Is there a patch for CVE-2026-55868?
Upgrade affected SRT libraries and tools to vendor-fixed packages. Debian 12 bookworm fixes are available in version 1.5.1-1+deb12u2, and Debian 13 trixie fixes are available in version 1.5.4-1+deb13u1.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.