cve.bz

CVE-2026-123805 SIPSorcery: Unbounded SCTP SACK gap/duplicate counts cause out-of-bounds read that kills the data-channel receive thread (DoS)

7.5 highEPSS 0.4%Fix available

High (7.5) in sipsorcery-org sipsorcery. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in SIPSorcery 10.0.14.

On this page
SIPSorcery is a WebRTC, SIP, and VoIP library for C# and .NET. Prior to 10.0.14, SctpSackChunk.ParseChunk reads the numGapAckBlocks and numDuplicateTSNs fields from an attacker-controlled SCTP SACK chunk without checking that the corresponding entries fit the declared chunk length. A negotiated WebRTC peer can send a checksum-valid malformed SACK chunk that drives the parser beyond the 262144-byte receive buffer. The resulting IndexOutOfRangeException bypasses the recoverable ApplicationException handler in RTCSctpTransport.DoReceive, causing the generic handler to exit the dedicated receive loop and permanently terminate the SCTP association and all data channels. This issue is fixed in 10.0.14.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-125 Out-of-bounds Read
CWE-755 Improper Handling of Exceptional Conditions
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-123805 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123805?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123805?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123805 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-123805

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-123805](https://cve.bz/cve/badge/CVE-2026-123805.svg)](https://cve.bz/cve/CVE-2026-123805)

HTML:

<a href="https://cve.bz/cve/CVE-2026-123805"><img src="https://cve.bz/cve/badge/CVE-2026-123805.svg" alt="CVE-2026-123805"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
sipsorcery-org sipsorcery< 10.0.14

Fix and patched versions

  • SIPSorcery (NuGet): fixed in 10.0.14

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jwjp-4649-v8jpNuGetSIPSorcery<10.0.1410.0.14

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON