CVE-2026-54887

MEDIUMNVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. 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
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use of Default Cryptographic Key vulnerability in Erlang/OTP ssl (DTLS server) allows predictable DTLS cookie computation during the startup window, enabling source address verification bypass.

On DTLS server startup, dtls_server_connection:initial_hello/3 initializes previous_cookie_secret to the empty binary (<<>>) instead of a random value. Because HMAC with an empty key is deterministic, anyone who observes the plaintext ClientHello can compute dtls_handshake:cookie(<<>>, IP, Port, Hello) and forge a valid DTLS cookie before the first rotation of the cookie secret. The DTLS cookie (RFC 6347 §4.2.1) is a denial-of-service mitigation that prevents spoofed source IPs from forcing the server to allocate state and perform expensive cryptographic operations; it is not an authentication mechanism. During the window from server startup until the first secret rotation (0 to 15 seconds), an attacker who can observe the plaintext ClientHello can bypass the source address verification, enabling DTLS handshake amplification with spoofed source addresses.

This vulnerability is associated with program file lib/ssl/src/dtls_server_connection.erl and program routine dtls_server_connection:initial_hello/3.

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

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/100

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
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

Published

July 2, 2026

Last Modified

July 24, 2026

Advisory Details (5)

Auto-updated Jul 3, 2026
Patch available. Sources: github_commit, github.
generic

Versions — Erlang System Documentation v29.0.3

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

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-54887
githubMentions a patch (unverified)

DTLS Cookie Bypass During Startup · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-p2m2-3c2w-8jp8
github_commit

commit 888e3bcd72d5 (erlang/otp)

Fix landed in erlang/otp commit 888e3bcd72d5 — awaiting tagged release

https://github.com/erlang/otp/commit/888e3bcd72d5406016b9e0de741026bc2a6f114d
generic

DTLS server cookie bypass during startup window due to empty initial cookie secret | Erlang Ecosystem Foundation CNA

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

Vendor Advisories for CVE-2026-54887(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.1+dfsg-1 (80 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 7× in last 7d / 33× 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 145 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54887?
CVE-2026-54887 is a medium vulnerability published on July 2, 2026. Use of Default Cryptographic Key vulnerability in Erlang/OTP ssl (DTLS server) allows predictable DTLS cookie computation during the startup window, enabling source address verification bypass. On DTLS server startup, dtlsserverconnection:initialhello/3 initializes previouscookiesecret to the empty…
When was CVE-2026-54887 disclosed?
CVE-2026-54887 was first published on July 2, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54887 actively exploited?
CVE-2026-54887 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54887?
CVE-2026-54887 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-54887?
A fix for CVE-2026-54887 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54887 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-54887

Explore →

Is Your Infrastructure Affected by CVE-2026-54887?

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