CVE-2026-54887 json
DTLS server cookie bypass during startup window due to empty initial cookie secret
published 2026-07-02 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-41411
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Erlang OTP 11.2.12.10, 11.6.0.3, 11.7.3, 27.3.4.14, 28.5.0.3, 29.0.3
- erlang Debian 13 1:27.3.4.1+dfsg-1+deb13u3
- erlang Debian 14 1:29.0.3+dfsg-1
debian advisories DEBIAN-CVE-2026-54887
- erlang Ubuntu 22.04 LTS 1:24.2.1+dfsg-1ubuntu0.8
- erlang Ubuntu 24.04 LTS 1:25.3.2.8+dfsg-1ubuntu4.8
- erlang Ubuntu 26.04 LTS 1:27.3.4.6+dfsg-1ubuntu0.2
- erlang Ubuntu Pro 18.04 LTS 1:20.2.2+dfsg-1ubuntu2+esm4
- erlang Ubuntu Pro 20.04 LTS 1:22.2.7+dfsg-1ubuntu0.5+esm3
ubuntu advisories UBUNTU-CVE-2026-54887
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- erlang SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +8 more 23.3.4.19-150300.3.39.1
- erlang26 SLES for SAP 15 SP6, SLES 15 SP6-LTSS, SLE Module for Server Applications 15 SP7 26.2.1-150300.7.28.1
suse advisories SUSE-SU-2026:3645-1SUSE-SU-2026:3579-1
- erlang openSUSE Tumbleweed 28.5.0.4-1.1
- erlang27 openSUSE Tumbleweed 27.1.3-3.1
opensuse advisories openSUSE-SU-2026:11559-1openSUSE-SU-2026:11560-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Erlang OTP
Classification
- Weakness
-
- CWE-1394 Use of Default Cryptographic Key
References
-
github.com
/erlang/otp/commit/888e3bcd72d5406016b9e0de741026bc2a6f114d
patch
-
github.com
/erlang/otp/security/advisories/GHSA-p2m2-3c2w-8jp8
vendor-advisory, related
-
cna.erlef.org
/cves/CVE-2026-54887.html
related, vendor-advisory
-
osv.dev
/vulnerability/EEF-CVE-2026-54887
related, third-party-advisory
-
erlang.org
/doc/system/versions.html#order-of-versions
release-notes
Sources
- CVE List CVE-2026-54887
- NVD CVE-2026-54887
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.