Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

SIPSorcery: Malformed UDP packet on the RTP/ICE socket can remotely terminate a media session (DoS)

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by SIPSorcery 10.0.9KEV status unknown

cve-program · CVE-2026-54632

Published

SIPSorcery is a WebRTC, SIP, and VoIP library for C# and .NET. Prior to 10.0.9, RTPChannel.OnRTPPacketReceived and the STUNAttribute.ParseMessageAttributes, STUNXORAddressAttribute, and STUNAddressAttribute parsing path index untrusted bytes without sufficient length checks, while UdpReceiver.EndReceiveFrom closes the channel when those operations raise a non-socket exception. A remote party can send a single short RTP packet or malformed zero-to-seven-byte STUN address attribute to the shared RTP/ICE socket, including during ICE connectivity checks before DTLS or STUN MESSAGE-INTEGRITY verification, and terminate the active RTP or WebRTC media session. The attacker must reach or learn the advertised ephemeral RTP/ICE port, but no authentication or user interaction is required, and the impact is limited to availability. This issue is fixed in version 10.0.9.

Read the publisher's advisory

euvd · EUVD-2026-78055

Published

SIPSorcery is a WebRTC, SIP, and VoIP library for C# and .NET. Prior to 10.0.9, RTPChannel.OnRTPPacketReceived and the STUNAttribute.ParseMessageAttributes, STUNXORAddressAttribute, and STUNAddressAttribute parsing path index untrusted bytes without sufficient length checks, while UdpReceiver.EndReceiveFrom closes the channel when those operations raise a non-socket exception. A remote party can send a single short RTP packet or malformed zero-to-seven-byte STUN address attribute to the shared RTP/ICE socket, including during ICE connectivity checks before DTLS or STUN MESSAGE-INTEGRITY verification, and terminate the active RTP or WebRTC media session. The attacker must reach or learn the advertised ephemeral RTP/ICE port, but no authentication or user interaction is required, and the impact is limited to availability. This issue is fixed in version 10.0.9.

Read the publisher's advisory

nvd · CVE-2026-54632

Published

SIPSorcery is a WebRTC, SIP, and VoIP library for C# and .NET. Prior to 10.0.9, RTPChannel.OnRTPPacketReceived and the STUNAttribute.ParseMessageAttributes, STUNXORAddressAttribute, and STUNAddressAttribute parsing path index untrusted bytes without sufficient length checks, while UdpReceiver.EndReceiveFrom closes the channel when those operations raise a non-socket exception. A remote party can send a single short RTP packet or malformed zero-to-seven-byte STUN address attribute to the shared RTP/ICE socket, including during ICE connectivity checks before DTLS or STUN MESSAGE-INTEGRITY verification, and terminate the active RTP or WebRTC media session. The attacker must reach or learn the advertised ephemeral RTP/ICE port, but no authentication or user interaction is required, and the impact is limited to availability. This issue is fixed in version 10.0.9.

Read the publisher's advisory

osv · GHSA-28gm-jrmw-xx93

Published

### Impact A single malformed inbound UDP packet on the RTP/ICE socket can remotely terminate an active RTP or WebRTC media session. The packet receive handler indexes packet (and STUN attribute) bytes without sufficient length checks and throws, and the UDP receive loop converted any such exception into a channel `Close` rather than dropping the packet. One small, unauthenticated packet therefore ends the media session. This is reachable during ICE connectivity checks — before the DTLS handshake and before any STUN `MESSAGE-INTEGRITY` verification. Because the RTP/ICE port is shared/advertised in the ICE candidates, a peer or on-path attacker can reach it (exposure is lower for a blind off-path attacker that must first learn the ephemeral port). Impact is availability only — no loss of confidentiality or integrity. ### Affected versions NuGet package `SIPSorcery` `<= 10.0.8`. ### Patches Fixed in `10.0.9`. ### Root cause Two issues combine: 1. **Unchecked indexing of untrusted bytes.** - `RTPChannel.OnRTPPacketReceived` read `packet[1]` after only checking the packet was non-empty, so a 1-byte packet threw `IndexOutOfRangeException`. - `STUNAttribute.ParseMessageAttributes` passed a `null`/short value to the typed attribute parsers, and `STUNXORAddressAttribute` (and the non-XOR `STUNAddressAttribute`) then read `attributeValue[1]`, `AsSpan(2)` and `AsSpan(4)` with no length check. A STUN message carrying an `XOR-MAPPED-ADDRESS`, `XOR-PEER-ADDRESS` or `XOR-RELAYED-ADDRESS` attribute of length 0–7 threw (`NullReferenceException` for length 0, `IndexOutOfRangeException`/`ArgumentOutOfRangeException` for 1–7). 2. **The UDP receive loop closed the channel on any exception.** The catch-all in `UdpReceiver.EndReceiveFrom` called `Close()`, tearing down the channel, instead of dropping the offending packet and continuing. This was systemic: any unhandled exception anywhere in the packet pipeline (STUN, RTP, RTCP, DTLS demux, SRTP, TURN) became a channel teardown. ### Fix - `UdpReceiver.EndReceiveFrom`: a non-socket exception now logs and drops the single packet and re-arms the receive loop (matching the existing `SIPUDPChannel` behaviour), instead of closing the channel. Genuine socket failures continue to be handled separately. - `RTPChannel.OnRTPPacketReceived`: requires a minimum packet length (`RTPHeader.MIN_HEADER_LEN`) before indexing the discriminator bytes. - STUN parsing: `ParseMessageAttributes` validates each attribute value length and skips malformed/truncated attributes; the XOR/address attribute constructors validate length defensively; `ParseSTUNMessage` no longer dereferences a null attribute list. Regression tests were added covering the 1-byte packet (channel stays open and remains usable), short/zero-length XOR address attributes (0–7 bytes), and truncated STUN messages. ### Workarounds None within the library short of upgrading. Restricting the RTP/ICE port to known peers at the network layer reduces exposure but does not eliminate it, since a negotiating peer can still trigger the condition. ### Credit Responsibly reported by Lokhesh Ujhoodha.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-54632

Published

sipsorcery

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "sipsorcery-org",
                    "product": "sipsorcery",
                    "versions": [
                        {
                            "version": "< 10.0.9",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-78055

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 14, 2026, 7:58:30 PM

dateUpdated: Sep 15, 2026, 2:43:28 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-54632

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-20 · CWE-755

Original publisher date fields

published: 2026-09-14T20:16:47.010

lastModified: 2026-09-30T17:51:56.193

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-28gm-jrmw-xx93

Published

SIPSorcery

NuGet

ECOSYSTEM · introduced 0 → fixed 10.0.9

110 versions listed as affected

1.3.0-PRE, 1.3.1, 1.4.0, 1.4.1, 1.5.0, 1.5.2, 1.5.3, 1.5.5, 1.5.6, 1.6.0, 1.6.1, 1.6.2, 10.0.1, 10.0.2, 10.0.3, 10.0.4-pre, 10.0.5, 10.0.6, 10.0.7, 10.0.8, 2.0.0, 2.0.1, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1.0, 3.2.0, 3.3.0, 3.4.0, 3.5.0, 3.6.0, 4.0.0-rc, 4.0.1-rc, 4.0.13-pre, 4.0.2-rc, 4.0.28-pre, 4.0.29-pre, 4.0.3-rc, 4.0.30-pre, 4.0.31-pre, 4.0.32-pre, 4.0.33-pre, 4.0.34-pre, 4.0.35-pre, 4.0.4-rc, 4.0.40-pre, 4.0.41-pre, 4.0.42-pre, 4.0.43-pre, 4.0.44-pre, 4.0.45-pre, 4.0.46-pre, 4.0.47-pre, 4.0.49-pre, 4.0.50-pre, 4.0.51-pre, 4.0.55-pre, 4.0.58-pre, 4.0.59-pre, 4.0.60-pre, 4.0.7-rc, 4.0.8-rc, 5.1.0, 5.1.1, 5.1.2, 5.1.4-pre, 5.1.5-pre, 5.1.6-pre, 5.1.7-pre, 5.1.8-pre, 5.2.0, 5.2.3, 5.3.0-pre, 5.3.3-pre, 6.0.1-pre, 6.0.11, 6.0.12, 6.0.2, 6.0.3, 6.0.4, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.1.0-pre, 6.1.1-pre, 6.2.0, 6.2.1, 6.2.3, 6.2.4, 8.0.0, 8.0.1, 8.0.10, 8.0.11, 8.0.12, 8.0.13, 8.0.14, 8.0.15-pre, 8.0.20-pre, 8.0.21-pre, 8.0.22, 8.0.23, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.9

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 10:01 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current