CVE-2026-68553

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-63077 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.13.0, an authenticated TURN user can place printf-style format specifiers in the STUN USERNAME or REALM attribute, which passes is_secure_string() validation and is embedded into Redis keys at nine call sites in src/apps/relay/ns_ioalib_engine_impl.c. send_message_to_redis() in src/apps/relay/hiredis_libevent2.c then passes the attacker-controlled key as the format argument to redisAsyncCommand() while supplying only one variadic value, causing hiredis redisvFormatCommand() to read past the va_list. Exploitation can crash the coturn process and terminate active TURN sessions or disclose stack memory into Redis. This issue is fixed in version 4.13.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.5%
EPSS %ILE
41st
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

August 19, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

4.13.0

Patch available: coturn/coturn 4.13.0

https://github.com/coturn/coturn/releases/tag/4.13.0
GitHub commit Patch Available

commit 8fa38032bb47 (coturn/coturn)

Patch available: coturn/coturn 4.13.0 (contains commit 8fa38032bb47)

https://github.com/coturn/coturn/commit/8fa38032bb4751e11e072d65a8eca3c06c950979
GitHub advisoryMentions a patch (unverified)

Format String Injection via TURN USERNAME/REALM into hiredis Redis Command · Advisory · coturn/coturn · GitHub

https://github.com/coturn/coturn/security/advisories/GHSA-4g7c-p5wg-j4hp

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1 ... 4.6.1-2 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1, 4.14.0-1, 4.15.0-1, 4.18.0-1, 4.6.1-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1, 4.6.1-2
  • every version up to 4.14.0-1: fixed in 4.14.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 135 rows 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. None are among the latest 100 rows. The 35 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-68553?
CVE-2026-68553 is a high-severity vulnerability; its CVE record was published on August 19, 2026. Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.13.0, an authenticated TURN user can place printf-style format specifiers in the STUN USERNAME or REALM attribute, which passes is_secure_string() validation and is embedded into Redis keys at nine call sites in…
When was the CVE record for CVE-2026-68553 published?
The CVE record for CVE-2026-68553 was published on August 19, 2026. 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-68553 actively exploited?
CVE-2026-68553 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68553?
CVE-2026-68553 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68553?
A fix for CVE-2026-68553 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-2026-68553

Explore →

Is Your Infrastructure Affected by CVE-2026-68553?

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

Book a Demo →Browse All CVEs