Publish Date: July 20, 2026
Severity: Critical
CVSS v3.1 Score: 9.1 / 9.1
Two critical security vulnerabilities (CVSS 9.1) have been identified and patched in the open-source SRT protocol library. Two CVEs have been published for these vulnerabilities.
It is recommended that you take immediate remediation action by updating to SRT protocol library v1.5.6, which contains fixes for both vulnerabilities.
The vulnerabilities affect all versions of the SRT protocol library prior to v1.5.6.
| CVE-2026-55869 | Heap-Based Buffer Overflow in KMREQ Handling |
| CVSS v3.1 | 9.1 (Critical) |
| Affected Software | Open-source SRT protocol library — all versions prior to 1.5.6 |
| Attack Vector | Network — single crafted UDP packet to any SRT endpoint (sender or receiver) during connection setup or key refresh |
| Authentication | None |
| Impact | Denial of service (immediate process crash), potential remote code execution |
Technical Description: A heap-based buffer overflow exists in the SRT protocol library when processing KMREQ control packets during connection setup and key refresh operations. A remote attacker can send a specially crafted packet that causes the SRT process to crash. No valid credentials, passphrase, or completed handshake are required.
| CVE-2026-55868 | Encryption State Machine Downgrade |
| CVSS v3.1 | 9.1 (Critical) |
| Affected Software | Open-source SRT protocol library — all versions prior to 1.5.6 |
| Attack Vector | Network — forged control packet targeting an active encrypted session |
| Authentication | None — SRT control packets carry no MAC authentication |
| Impact | Silent encryption bypass, stream hijacking, content injection |
Technical Description: SRT control packets carry no Message Authentication Code (MAC). An attacker who has network access to the receiver’s listening port, or who can observe an active session’s 5-tuple (source IP, source port, destination IP, destination port, SRT socket ID) and send spoofed packets to the receiver, can send a forged KMREQ control message that causes the receiver’s encryption state to transition from SECURED to BADSECRET. Once downgraded, the receiver accepts unencrypted data packets from any sender, enabling stream hijacking, content injection, and interception of live media.
Regardless of patch status, we recommend:
It is recommended that you take immediate remediation action by updating to SRT protocol library v1.5.6, which contains fixes for both vulnerabilities. The vulnerabilities affect all versions of the SRT protocol library prior to v1.5.6.
This update does not affect existing connections or interoperability, allowing you to take a phased approach to upgrading endpoints across your workflow.
These vulnerabilities were reported through responsible disclosure by:
We thank both parties for their responsible coordination.
For questions or assistance: director@srtalliance.org