Quick answers
- Is CVE-2026-102716 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102716 being exploited in the wild.
- How severe is CVE-2026-102716?
- Informational severity, published 29 September 2026.
- Which products and versions are affected?
- Microsoft NetX affected versions unspecified.
- Is there a fix for CVE-2026-102716?
- 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-102716 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102716?
- Check whether you run Microsoft NetX 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
An RTSP parser in NetX returns a raw NetX error code instead of an RTSP status code when the Session header cannot be parsed, causing the error handler to take an unrecognized code path that fails to release an already-allocated response packet. The vulnerability allows unauthenticated network clients to trigger this condition repeatedly, exhausting the shared packet pool and causing denial of service to the RTSP server and potentially other components using the same memory allocator.
Affected products
- Microsoft NetX affected versions unspecified
Timeline
- 2026-09-29: disclosed