Quick answers
- Is CVE-2026-38998 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38998 being exploited in the wild.
- How severe is CVE-2026-38998?
- Medium severity, with a CVSS score of 6.5, published 9 September 2026.
- Which products and versions are affected?
- LIVE555 Streaming Media 2026.02.26 and earlier.
- Is there a fix for CVE-2026-38998?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-38998 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-38998?
- Check whether you run LIVE555 Streaming Media at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a use-after-free flaw in the SocketDescriptor::tcpReadHandler1 function (liveMedia/RTPInterface.cpp:536). A buffer allocated during RTSPServer::createNewClientConnection is freed in the RTSPClientConnection destructor, but the handler continues to reference the freed memory, leading to a crash. The attack vector is network-based, requiring only the ability to send crafted RTSP and HTTP requests to the streaming server. No authentication or special preconditions are required. An attacker can achieve denial of service by crashing the streaming server. A fix is expected in version 2026.09.23 or later based on the changelog.
Affected products
- LIVE555 Streaming Media 2026.02.26 and earlier
Timeline
- 2026-03-20: disclosed: Vulnerability reported to LIVE555 mailing list
- 2026-09-09: advisory: CVE-2026-38998 published