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.
CVE-2026-73212
This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(medium)
- EG Risk
- 26(Track)EG Risk 26/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 11, 2026
Advisory Details (6)
Auto-updated Aug 11, 2026coturn peer-IP ACL canonicalization & scope bypass on the RFC 6062 TCP CONNECT relay path → internal-network SSRF and proven internal root RCE · Advisory · coturn/coturn · GitHub
https://github.com/coturn/coturn/security/advisories/GHSA-2x4g-wx24-48m44.13.1
Patch available: coturn/coturn 4.13.1
https://github.com/coturn/coturn/releases/tag/4.13.1Deny link-local / ULA / site-local relay peers by default
Patch available: coturn/coturn 4.13.1 (PR #1947 merged 2026-06-15)
https://github.com/coturn/coturn/pull/1947Canonicalize all IPv4-in-IPv6 encodings before peer-IP checks
Patch available: coturn/coturn 4.13.1 (PR #1945 merged 2026-06-15)
https://github.com/coturn/coturn/pull/1945commit d49ee56aa9fe (coturn/coturn)
Patch available: coturn/coturn 4.13.1 (contains commit d49ee56aa9fe)
https://github.com/coturn/coturn/commit/d49ee56aa9fe748af064853d5e430eec1ccc3cbccommit cf4b4952de48 (coturn/coturn)
Patch available: coturn/coturn 4.13.1 (contains commit cf4b4952de48)
https://github.com/coturn/coturn/commit/cf4b4952de48510d38415b96300da5fc674bfddaWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 39× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 08:09 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 09:08 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 01:39 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:39 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 03:39 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:40 UTCEG score recompute
- 2026-08-23 06:40 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 07:41 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 08:41 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 09:41 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:42 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 11:38 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:39 UTCEG score recompute
Show 14 moreShow fewer
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:39 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 14:39 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 15:38 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 17:36 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 18:37 UTCEG score recompute
- 2026-08-11 18:06 UTCEG score recompute
- 2026-08-11 17:37 UTCEG score recompute
- 2026-08-11 17:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-284 · CWE-918
- CVE-2014-6626EG 10.0HIGH
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
- CVE-2010-5305EG 9.8EPSS p95CRITICAL
- CVE-2014-10059EG 9.8CRITICAL
- CVE-2014-10053EG 9.8CRITICAL
- CVE-2014-10050EG 9.8CRITICAL
- CVE-2014-2048EG 9.8CRITICAL
- CVE-2014-3990EG 9.8EPSS p93CRITICAL
- CVE-2014-3624EG 9.8CRITICAL
- CVE-2014-9148EG 9.8EPSS p95CRITICAL
Frequently asked(5)
What is CVE-2026-73212?
When was CVE-2026-73212 disclosed?
Is CVE-2026-73212 actively exploited?
What is the CVSS score of CVE-2026-73212?
How do I remediate CVE-2026-73212?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73212
Is Your Infrastructure Affected by CVE-2026-73212?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.