Vulnerability in SIPSorcery (CVE-2026-54632)
Summary
Vulnerability in SIPSorcery (CVE-2026-54632). Risk of unauthorized operations or information disclosure. Exploitable via Close. Mitigation: upgrade to 10.0.9 or later.
Original description
The description as published by the source.
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:
- Unchecked indexing of untrusted bytes.
RTPChannel.OnRTPPacketReceivedreadpacket[1]after only checking the packet was non-empty, so a 1-byte packet threwIndexOutOfRangeException.STUNAttribute.ParseMessageAttributespassed anull/short value to the typed attribute parsers, andSTUNXORAddressAttribute(and the non-XORSTUNAddressAttribute) then readattributeValue[1],AsSpan(2)andAsSpan(4)with no length check. A STUN message carrying anXOR-MAPPED-ADDRESS,XOR-PEER-ADDRESSor `XOR-REL…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54632 has been found in SIPSorcery.
Attackers can target a specific entry point like Close over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade SIPSorcery to 10.0.9 or later.
If unsure, ask your IT team or search "SIPSorcery CVE-2026-54632" on the vendor's site.
CVE-2026-54632 (SIPSorcery) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Close / SIPSorcery / RTPChannel.OnRTPPacketReceived / IndexOutOfRangeException
Patched: 10.0.9 — apply immediately
Workaround: None within the library short of upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in SIPSorcery. Attackers reach the vulnerable code path via Close without authentication.
Check the vendor advisory for the affected versions of SIPSorcery. Attack surface: Close / SIPSorcery / RTPChannel.OnRTPPacketReceived / IndexOutOfRangeException.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 10.0.9.
Workaround: None within the library short of upgrading.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'SIPSorcery' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'SIPSorcery' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
SIPSorceryを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
None within the library short of upgrading.パッチが適用されるまでの応急処置として、None within the library short of upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade SIPSorcery to 10.0.9ステージング環境で 10.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com