CVE-2026-68554

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th 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, secondary
Elevated
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.15.0, an on-path attacker can append attributes after MESSAGE-INTEGRITY to an authenticated STUN request on plain UDP or TCP, adjust the STUN header length, and recompute the unkeyed FINGERPRINT while the original HMAC remains valid because it covers only the message prefix. Server-side parsing in src/server/ns_turn_server.c continues past MESSAGE-INTEGRITY through handle_turn_allocate(), handle_turn_create_permission(), handle_turn_refresh(), and handle_turn_command(), allowing trailing LIFETIME, XOR-PEER-ADDRESS, or ORIGIN attributes to override allocation lifetime, inject a permission, or bypass the origin check. TLS and DTLS deployments prevent this in-transit modification. This issue is fixed in version 4.15.0.

CVSS v3
2.3
EG Score
2.3LOWmedium confidence
EG Risk
26
EG Risk 26/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
Severity23% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack 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). 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

August 19, 2026

Last Modified

September 9, 2026

References (4)

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1, 4.14.0-1, 4.15.0-1, 4.6.1-1, 4.6.1-2
  • 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.6.1-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1, 4.14.0-1, 4.6.1-2
  • every version up to 4.15.0-1: fixed in 4.15.0-1
—

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-07 02:20 UTCEG score recompute
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-04 02:40 UTCEG score recompute
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-02 17:56 UTCEPSS rescore
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-10-01 01:21 UTCEG score recompute
  13. 2026-09-30 15:03 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 00:28 UTCEG score recompute
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 00:48 UTCEG score recompute
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-21 21:21 UTCEG score recompute
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-18 21:41 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 30 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 21:55 UTCEG score recompute
  3. 2026-09-12 22:16 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-09 22:34 UTCEG score recompute
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-07 15:37 UTCEG score recompute
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 12:51 UTCEG score recompute
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 13:11 UTCEG score recompute
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-29 13:32 UTCEG score recompute
  19. 2026-08-28 21:42 UTCEPSS rescore
  20. 2026-08-26 13:46 UTCEG score recompute
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-23 14:06 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:56 UTCEPSS rescore
  26. 2026-08-20 14:25 UTCEG score recompute
  27. 2026-08-20 13:52 UTCEG score recompute
  28. 2026-08-19 21:19 UTCEG score recompute
  29. 2026-08-19 20:54 UTCEG score recompute
  30. 2026-08-19 20:52 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-68554?
CVE-2026-68554 is a low vulnerability published on August 19, 2026. Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.15.0, an on-path attacker can append attributes after MESSAGE-INTEGRITY to an authenticated STUN request on plain UDP or TCP, adjust the STUN header length, and recompute the unkeyed FINGERPRINT while the original HMAC…
When was CVE-2026-68554 disclosed?
CVE-2026-68554 was first published on August 19, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68554 actively exploited?
CVE-2026-68554 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68554?
CVE-2026-68554 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68554?
A fix for CVE-2026-68554 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-68554

Explore →

Is Your Infrastructure Affected by CVE-2026-68554?

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

Book a Demo →Browse All CVEs