CVE-2026-55663 json
mediasoup: SCTP state cookie lacks cryptographic authentication, enabling unauthorized association establishment (RFC 9260 violation)
published 2026-08-25 2 mo ago modified 2026-09-09 1 mo ago also GHSA-p7x2-g5cq-fhmq , EUVD-2026-65694
- cvss
- 5.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
mediasoup is a WebRTC video conferencing system. From version 3.20.0 until 3.20.6 for the npm package and from 0.22.0 until 0.22.5 for the Rust crate, mediasoup's built-in SCTP stack authenticates state cookies using only the hardcoded msworker and 0xAD81 magic values instead of a per-instance secret and HMAC, contrary to RFC 9260 Section 5.1.3. The cookie structure and validation in worker/include/RTC/SCTP/association/StateCookie.hpp and worker/src/RTC/SCTP/association/StateCookie.cpp allow an on-path attacker targeting PlainTransport or PipeTransport with SCTP enabled and without DTLS protection to forge a COOKIE-ECHO whose packet verification tag matches the attacker-controlled localVerificationTag. The forged cookie passes StateCookie::IsMediasoupStateCookie() and Association::HandleReceivedCookieEchoChunk(), establishes an unauthorized SCTP association, and permits DataChannel message injection as a trusted peer. WebRtcTransport is not affected because its SCTP runs inside DTLS. This issue is fixed in npm version 3.20.6 and Rust crate version 0.22.5.
Patch / fix
- npm mediasoup 3.20.6
- crates.io mediasoup 0.22.5
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/versatica/mediasoup/security/advisories/GHSA-p7x2-g5cq-fhmq referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.6 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 5.6 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | mediasoup | >=3.20.0, <3.20.6 |
3.20.6 |
| crates.io | mediasoup | >=0.22.0, <0.22.5 |
0.22.5 |
Affected products
- versatica mediasoup
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
github.com
/versatica/mediasoup/pull/1829
web
-
github.com
/versatica/mediasoup/commit/9c1a90a8f9206b965e727d134846fb42df4980a7
web
-
github.com
/versatica/mediasoup/security/advisories/GHSA-p7x2-g5cq-fhmq
exploit, web
-
github.com
/versatica/mediasoup/releases/tag/3.20.6
web
-
github.com
/versatica/mediasoup
package
Sources
- CVE List CVE-2026-55663
- GitHub Advisory GHSA-p7x2-g5cq-fhmq
- NVD CVE-2026-55663
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.