CVE-2026-55950

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th 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-2026-41414 (ENISA EUVD)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Time-of-check Time-of-use (TOCTOU) race condition vulnerability in Erlang/OTP ssl (dtls_packet_demux module) allows an unauthenticated remote attacker to crash all active DTLS sessions on a listener.

A DTLS server listener uses a single shared dtls_packet_demux gen_server process to route incoming UDP datagrams to the correct connection handler. When a DTLS client reconnects rapidly from the same source address and port (sending multiple ClientHello messages in quick succession), a race condition in the demux's internal gb_trees key-value store causes a {key_exists, {old, Client}} crash, terminating the demux process. Because the demux is shared across all DTLS associations on that listener, its crash immediately kills every active DTLS session, not just the attacker's.

The attack is pre-authentication: the attacker only needs to send UDP datagrams containing valid ClientHello messages from the same source IP and port before the intermediate DOWN monitor message is processed by the gen_server. No credentials, no completed handshake, and no special configuration are required, and the crash can be repeated indefinitely to create a persistent denial of service for all clients of that listener.

This vulnerability is associated with program file lib/ssl/src/dtls_packet_demux.erl.

This issue affects OTP from OTP 25.3 before OTP 27.3.4.14, OTP 28.5.0.3, and OTP 29.0.3, corresponding to ssl from 10.9 before 11.2.12.10, 11.6.0.3, and 11.7.3.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
42
EG Risk 42/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)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
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 (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-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. 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; 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 (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 2, 2026

Last Modified

November 11, 2026

Advisory Details (5)

Auto-updated Jul 2, 2026
Patch available. Sources: github_commit, github.
Web page

Versions — Erlang System Documentation v29.0.3

https://www.erlang.org/doc/system/versions.html#order-of-versions
Web page

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-55950
GitHub advisoryMentions a patch (unverified)

DTLS Denial of Service · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-hwfc-5hf4-gvr3
GitHub commit

commit e44d2bf01c44 (erlang/otp)

Fix landed in erlang/otp commit e44d2bf01c44 — awaiting tagged release

https://github.com/erlang/otp/commit/e44d2bf01c4473ef2ea7f09e3523cf96de6e4a04
Web page

DTLS listener crash via race condition in dtls_packet_demux causes denial of service for all sessions | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-55950.html

Vendor Advisories for CVE-2026-55950(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:25.2.3+dfsg-1 ... 1:29.1.2+dfsg-1 (81 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1, 1:27.3.4.1+dfsg-1+deb13u1, 1:27.3.4.1+dfsg-1+deb13u2
  • every version up to 1:27.3.4.1+dfsg-1+deb13u3: fixed in 1:27.3.4.1+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (34 versions)
  • every version up to 1:29.0.3+dfsg-1: fixed in 1:29.0.3+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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 198 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 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-55950?
CVE-2026-55950 is a medium-severity vulnerability; its CVE record was published on July 2, 2026. Time-of-check Time-of-use (TOCTOU) race condition vulnerability in Erlang/OTP ssl (dtls_packet_demux module) allows an unauthenticated remote attacker to crash all active DTLS sessions on a listener. A DTLS server listener uses a single shared dtls_packet_demux gen_server process to route incoming…
When was CVE-2026-55950 made public?
CVE-2026-55950 was made public on July 2, 2026: that is the date its CVE record's CNA, Erlang Ecosystem Foundation, gives for when the vulnerability was made public. The CVE record itself was published on July 2, 2026. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-55950 actively exploited?
CVE-2026-55950 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55950?
CVE-2026-55950 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-55950?
A fix for CVE-2026-55950 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55950 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55950

Explore →

Is Your Infrastructure Affected by CVE-2026-55950?

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