CVE-2020-26262

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 1.5% (73rd percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 7.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Coturn is free open source implementation of TURN and STUN Server. Coturn before version 4.5.2 by default does not allow peers to connect and relay packets to loopback addresses in the range of 127.x.x.x. However, it was observed that when sending a CONNECT request with the XOR-PEER-ADDRESS value of 0.0.0.0, a successful response was received and subsequently, CONNECTIONBIND also received a successful response. Coturn then is able to relay packets to the loopback interface. Additionally, when coturn is listening on IPv6, which is default, the loopback interface can also be reached by making use of either [::1] or [::] as the peer address. By using the address 0.0.0.0 as the peer address, a malicious user will be able to relay packets to the loopback interface, unless --denied-peer-ip=0.0.0.0 (or similar) has been specified. Since the default configuration implies that loopback peers are not allowed, coturn administrators may choose to not set the denied-peer-ip setting. The issue patched in version 4.5.2. As a workaround the addresses in the address block 0.0.0.0/8, [::1] and [::] should be denied by default unless --allow-loopback-peers has been specified.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

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 computed
Severity72% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
74th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 13, 2021

Last Modified

November 21, 2024

References (10)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucoturn (4.5.0.3-1ubuntu0.4) @ xenial2026-05-26ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.5.1.1-1.1, 4.5.1.1-1.1+deb10u1
  • every version up to 4.5.1.1-1.1+deb10u2: fixed in 4.5.1.1-1.1+deb10u2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
coturn—
  • every version up to 4.5.2-1: fixed in 4.5.2-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
coturn—
  • every version up to 4.5.2-1: fixed in 4.5.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
coturn—
  • every version up to 4.5.2-1: fixed in 4.5.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
coturn—
  • every version up to 4.5.2-1: fixed in 4.5.2-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.5.0.5-1, 4.5.0.5-1+deb9u1, 4.5.0.5-1+deb9u2
  • every version up to 4.5.0.5-1+deb9u3: fixed in 4.5.0.5-1+deb9u3
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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.

Showing the most recent 100 of 163 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:38 UTCEPSS rescore
  3. 2026-10-07 23:44 UTCEPSS rescore
  4. 2026-10-06 15:13 UTCEPSS rescore
  5. 2026-10-05 17:39 UTCEPSS rescore
  6. 2026-10-03 14:22 UTCEPSS rescore
  7. 2026-09-30 15:16 UTCEG score recompute
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-29 15:14 UTCEPSS rescore
  10. 2026-09-27 13:41 UTCEPSS rescore
  11. 2026-09-26 15:54 UTCEPSS rescore
  12. 2026-09-26 15:54 UTCEPSS rescore
  13. 2026-09-26 13:55 UTCOSV refresh
  14. 2026-09-24 14:00 UTCEPSS rescore
  15. 2026-09-22 14:43 UTCEPSS rescore
  16. 2026-09-21 20:28 UTCEPSS rescore
  17. 2026-09-20 20:11 UTCEPSS rescore
  18. 2026-09-19 15:37 UTCEPSS rescore
  19. 2026-09-18 19:23 UTCEPSS rescore
  20. 2026-09-17 19:22 UTCEPSS rescore
  21. 2026-09-16 14:04 UTCEPSS rescore
  22. 2026-09-15 03:06 UTCEPSS rescore
  23. 2026-09-13 16:43 UTCEPSS rescore
  24. 2026-09-12 14:57 UTCEPSS rescore
  25. 2026-09-11 09:32 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 21:56 UTCEPSS rescore
  2. 2026-09-07 15:57 UTCEPSS rescore
  3. 2026-09-07 00:19 UTCOSV refresh
  4. 2026-09-06 13:44 UTCEPSS rescore
  5. 2026-09-05 15:24 UTCEPSS rescore
  6. 2026-09-04 13:57 UTCEPSS rescore
  7. 2026-09-04 05:03 UTCEPSS rescore
  8. 2026-09-02 14:08 UTCEPSS rescore
  9. 2026-09-01 03:32 UTCEPSS rescore
  10. 2026-08-30 19:14 UTCEPSS rescore
  11. 2026-08-30 01:18 UTCEPSS rescore
  12. 2026-08-27 14:21 UTCEPSS rescore
  13. 2026-08-26 14:42 UTCEPSS rescore
  14. 2026-08-25 13:45 UTCEPSS rescore
  15. 2026-08-21 23:45 UTCEPSS rescore
  16. 2026-08-20 22:52 UTCEPSS rescore
  17. 2026-08-20 10:31 UTCOSV refresh
  18. 2026-08-19 17:00 UTCEPSS rescore
  19. 2026-08-18 13:44 UTCEPSS rescore
  20. 2026-08-17 13:43 UTCEPSS rescore
  21. 2026-08-16 14:52 UTCEPSS rescore
  22. 2026-08-16 02:11 UTCEPSS rescore
  23. 2026-08-15 01:26 UTCEPSS rescore
  24. 2026-08-13 21:57 UTCEPSS rescore
  25. 2026-08-12 13:47 UTCEPSS rescore
  26. 2026-08-09 13:43 UTCEPSS rescore
  27. 2026-08-08 16:33 UTCEPSS rescore
  28. 2026-08-07 16:23 UTCEPSS rescore
  29. 2026-08-06 13:43 UTCEPSS rescore
  30. 2026-08-05 05:41 UTCOSV refresh
  31. 2026-08-04 15:06 UTCEPSS rescore
  32. 2026-08-04 10:34 UTCEPSS rescore
  33. 2026-08-02 02:23 UTCEPSS rescore
  34. 2026-08-01 04:12 UTCEPSS rescore
  35. 2026-07-30 16:25 UTCEPSS rescore
  36. 2026-07-30 01:27 UTCEPSS rescore
  37. 2026-07-28 15:33 UTCEPSS rescore
  38. 2026-07-26 14:51 UTCEPSS rescore
  39. 2026-07-25 14:15 UTCEPSS rescore
  40. 2026-07-24 14:14 UTCEPSS rescore
  41. 2026-07-23 14:15 UTCEPSS rescore
  42. 2026-07-23 14:15 UTCEPSS rescore
  43. 2026-07-23 01:51 UTCEG score recompute
  44. 2026-07-22 22:37 UTCEG score recompute
  45. 2026-07-22 14:05 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-21 15:22 UTCEPSS rescore
  48. 2026-07-20 17:04 UTCEPSS rescore
  49. 2026-07-20 17:04 UTCEPSS rescore
  50. 2026-07-19 14:28 UTCEPSS rescore
  51. 2026-07-19 14:28 UTCEPSS rescore
  52. 2026-07-19 04:22 UTCOSV refresh
  53. 2026-07-19 02:26 UTCEPSS rescore
  54. 2026-07-19 02:26 UTCEPSS rescore
  55. 2026-07-16 16:59 UTCEPSS rescore
  56. 2026-07-15 16:55 UTCEPSS rescore
  57. 2026-07-15 16:55 UTCEPSS rescore
  58. 2026-07-15 01:57 UTCEPSS rescore
  59. 2026-07-13 22:27 UTCEPSS rescore
  60. 2026-07-13 22:27 UTCEPSS rescore
  61. 2026-07-13 06:10 UTCEPSS rescore
  62. 2026-07-13 06:10 UTCEPSS rescore
  63. 2026-07-12 05:44 UTCEPSS rescore
  64. 2026-07-11 08:25 UTCEPSS rescore
  65. 2026-07-11 08:25 UTCEPSS rescore
  66. 2026-07-09 19:07 UTCEPSS rescore
  67. 2026-07-08 15:12 UTCEPSS rescore
  68. 2026-07-07 13:43 UTCEPSS rescore
  69. 2026-07-06 16:25 UTCEPSS rescore
  70. 2026-07-06 16:25 UTCEPSS rescore
  71. 2026-07-06 02:21 UTCEPSS rescore
  72. 2026-07-06 02:21 UTCEPSS rescore
  73. 2026-07-04 06:29 UTCEPSS rescore
  74. 2026-07-04 06:29 UTCEPSS rescore
  75. 2026-07-01 10:48 UTCOSV refresh

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2020-26262?
CVE-2020-26262 is a high vulnerability published on January 13, 2021. Coturn is free open source implementation of TURN and STUN Server. Coturn before version 4.5.2 by default does not allow peers to connect and relay packets to loopback addresses in the range of 127.x.x.x. However, it was observed that when sending a CONNECT request with the XOR-PEER-ADDRESS value…
When was CVE-2020-26262 disclosed?
CVE-2020-26262 was first published on January 13, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-26262 actively exploited?
CVE-2020-26262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-26262?
CVE-2020-26262 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2020-26262?
A fix for CVE-2020-26262 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-26262

Explore →

Is Your Infrastructure Affected by CVE-2020-26262?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs