Is CVE-2026-54632 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54632 being exploited in the wild.

How severe is CVE-2026-54632?

High severity, with a CVSS score of 7.5, published 14 September 2026.

Which products and versions are affected?

SIPSorcery (NuGet) <= 10.0.8, ECOSYSTEM:introduced=0,fixed=10.0.9.

Is there a fix for CVE-2026-54632?

Yes. SIPSorcery (NuGet): upgrade to 10.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54632 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54632?

Check whether you run SIPSorcery (NuGet) 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.

CVE-2026-54632: SIPSorcery remote denial of service via malformed UDP packet

Q: Which products and versions are affected?

SIPSorcery (NuGet) <= 10.0.8, ECOSYSTEM:introduced=0,fixed=10.0.9.

Q: Is there a fix for CVE-2026-54632?

Yes. SIPSorcery (NuGet): upgrade to 10.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-54632 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-54632?

Check whether you run SIPSorcery (NuGet) 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.

CVE-2026-54632 · Severity: high · CVSS 7.5 · Published 2026-09-14

SIPSorcery is a library used to build real-time communication applications like VoIP and WebRTC video calls. A vulnerability allows a remote attacker to terminate active media sessions by sending a single specially crafted network packet. This can lead to service disruptions and dropped calls for users of the affected software.

Technologies: SIPSorcery (NuGet). Vendors: NuGet.

Quick answers

Is CVE-2026-54632 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54632 being exploited in the wild.
How severe is CVE-2026-54632?: High severity, with a CVSS score of 7.5, published 14 September 2026.
Which products and versions are affected?: SIPSorcery (NuGet) <= 10.0.8, ECOSYSTEM:introduced=0,fixed=10.0.9.
Is there a fix for CVE-2026-54632?: Yes. SIPSorcery (NuGet): upgrade to 10.0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54632 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54632?: Check whether you run SIPSorcery (NuGet) 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.

How to fix

SIPSorcery (NuGet): upgrade to 10.0.9 or later

dotnet add package SIPSorcery --version 10.0.9

Technical details

The vulnerability stems from two combined issues: improper input validation and improper exception handling. Specifically, 'RTPChannel.OnRTPPacketReceived' and 'STUNAttribute.ParseMessageAttributes' perform unchecked indexing on untrusted bytes from inbound UDP packets, leading to 'IndexOutOfRangeException' or 'NullReferenceException' when processing malformed or truncated packets. Furthermore, the UDP receive loop in 'UdpReceiver.EndReceiveFrom' was designed to close the entire channel upon encountering any exception rather than dropping the invalid packet. An unauthenticated remote attacker can exploit this during ICE connectivity checks to cause a Denial of Service (DoS). The issue is fixed in version 10.0.9.

Affected products

sipsorcery-org SIPSorcery <= 10.0.8

Identifiers

CVE-2026-54632
GHSA-28gm-jrmw-xx93

Timeline

2026-07-28: advisory: GitHub Advisory published
2026-07-28: patched: Fixed in version 10.0.9

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.