CVE-2026-73212 json
coturn peer-IP ACL canonicalization & scope bypass on the RFC 6062 TCP CONNECT relay path → internal-network SSRF and proven internal root RCE
published 3mo ago modified 2mo ago also EUVD-2026-56789
- cvss
- 5.8
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.13.1, good_peer_addr() in src/server/ns_turn_server.c uses ioa_addr_in_range() in src/client/ns_turn_ioaddr.c without canonicalizing IPv4-compatible, 6to4, and 64:ff9b::/96 NAT64 address forms, allowing an authenticated RFC 6062 TCP CONNECT relay client to bypass an IPv4 denied-peer-ip range when the Coturn host has a useful translation route. This issue is fixed in version 4.13.1.
Patch / fix
- coturn_project coturn 4.13.1
- coturn Debian 14 4.14.0-1
debian advisories DEBIAN-CVE-2026-73212
- coturn openSUSE Tumbleweed 4.17.2-1.1
opensuse advisories openSUSE-SU-2026:11617-1
- github.com/coturn/coturn@cf4b495 commit
- github.com/coturn/coturn@d49ee56 commit
- github.com/coturn/coturn#1945 pull request
- github.com/coturn/coturn#1947 pull request
- github.com/coturn/coturn/releases/tag/4.13.1 release
Is CVE-2026-73212 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-73212 updated cvss 7.7
coturn: Coturn: Server-Side Request Forgery and Remote Code Execution via IP address canonicalization bypass
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.8 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H |
| CNA | 4.0 | 5.8 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- coturn coturn
Classification
References
- github.com /coturn/coturn/pull/1945
- github.com /coturn/coturn/pull/1947
- github.com /coturn/coturn/commit/cf4b4952de48510d38415b96300da5fc674bfdda
- github.com /coturn/coturn/commit/d49ee56aa9fe748af064853d5e430eec1ccc3cbc
- github.com /coturn/coturn/security/advisories/GHSA-2x4g-wx24-48m4
- github.com /coturn/coturn/releases/tag/4.13.1
Sources
- CVE List CVE-2026-73212
- NVD CVE-2026-73212
Fencer Intel 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.