CVE-2025-69217

HIGHNVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2025-205680 (ENISA EUVD)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

coturn is a free open source implementation of TURN and STUN Server. Versions 4.6.2r5 through 4.7.0-r4 have a bad random number generator for nonces and port randomization after refactoring. Additionally, random numbers aren't generated with openssl's RAND_bytes but libc's random() (if it's not running on Windows). When fetching about 50 sequential nonces (i.e., through sending 50 unauthenticated allocations requests) it is possible to completely reconstruct the current state of the random number generator, thereby predicting the next nonce. This allows authentication while spoofing IPs. An attacker can send authenticated messages without ever receiving the responses, including the nonce (requires knowledge of the credentials, which is e.g., often the case in IoT settings). Since the port randomization is deterministic given the pseudorandom seed, an attacker can exactly reconstruct the ports and, hence predict the randomization of the ports. If an attacker allocates a relay port, they know the current port, and they are able to predict the next relay port (at least if it is not used before). Commit 11fc465f4bba70bb0ad8aae17d6c4a63a29917d9 contains a fix.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 30, 2025

Last Modified

October 13, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Unsafe nonce and relay port randomization due to weak random number generation. · Advisory · coturn/coturn · GitHub

https://github.com/coturn/coturn/security/advisories/GHSA-fvj6-9jhg-9j84
GitHub commit Patch Available

commit 88ced4713858 (coturn/coturn)

Patch available: coturn/coturn 4.7.0 (contains commit 88ced4713858)

https://github.com/coturn/coturn/commit/88ced471385869d7e7fbbc4766e78ef521b36af6
GitHub commit Patch Available

commit 11fc465f4bba (coturn/coturn)

Patch available: coturn/coturn 4.8.0 (contains commit 11fc465f4bba)

https://github.com/coturn/coturn/commit/11fc465f4bba70bb0ad8aae17d6c4a63a29917d9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 219 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-69217?
CVE-2025-69217 is a high-severity vulnerability; its CVE record was published on December 30, 2025. coturn is a free open source implementation of TURN and STUN Server. Versions 4.6.2r5 through 4.7.0-r4 have a bad random number generator for nonces and port randomization after refactoring. Additionally, random numbers aren't generated with openssl's RAND_bytes but libc's random() (if it's not…
When was the CVE record for CVE-2025-69217 published?
The CVE record for CVE-2025-69217 was published on December 30, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2025-69217 actively exploited?
CVE-2025-69217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-69217?
CVE-2025-69217 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2025-69217?
A fix for CVE-2025-69217 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-69217

Explore →

Is Your Infrastructure Affected by CVE-2025-69217?

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

Book a Demo →Browse All CVEs