# CVE-2026-123805: SIPSorcery vulnerable to Denial of Service via out-of-bounds read in SCTP SACK chunk parsing


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-jwjp-4649-v8jp

## What is CVE-2026-123805?

CVE-2026-123805 is a high-severity vulnerability in sipsorcery-org sipsorcery, published on 9 Nov 2026. 

### Official description

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.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-123805?

1 open source package ship an affected version, including SIPSorcery.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `SIPSorcery` | NuGet | All versions | 10.0.14 |

## How do I fix CVE-2026-123805?

Upgrade SIPSorcery to 10.0.14 or later.

## Is CVE-2026-123805 being exploited?

There is no known exploitation of CVE-2026-123805 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123805 and fix it if it is affected.

What it is: CVE-2026-123805 is a high-severity vulnerability in sipsorcery-org sipsorcery, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123805 in the wild and no public exploit code.

Affected packages and fixed versions:
- SIPSorcery (NuGet): affected all versions; fixed in 10.0.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123805/ (Markdown: https://insights.sbomify.com/CVE-2026-123805/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123805
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123805
- OSV: https://osv.dev/vulnerability/CVE-2026-123805

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123805/
Summaries are generated and may contain mistakes; the official description above is the record.