Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 84%

CVE-2026-54887: CWE-1394 Use of Default Cryptographic Key in Erlang OTP

0
Medium
VulnerabilityCVE-2026-54887cvecve-2026-54887cwe-1394
Published: 07/02/2026 (07/02/2026, 16:06:04 UTC)
Source: CVE Database V5
Vendor/Project: Erlang
Product: OTP

Description

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 v4.0

Score 6.3medium

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
None
Vuln. Integrity
None
Vuln. Availability
Low
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

GitHub Actionsmore threats →cve
ssl
pkg:github/ssl
Affected versions
=8.2
GitHub Actionsmore threats →cve
erlang/otp
pkg:github/erlang/otp
Affected versions
=20.0
CPE configurations
cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/24/2026, 21:37:16 UTC

Technical Analysis

This vulnerability arises because the DTLS server in Erlang/OTP initializes the previous_cookie_secret to an empty binary instead of a random value during startup. Since HMAC with an empty key is deterministic, an attacker who observes the ClientHello message can compute the DTLS cookie before the first secret rotation (which occurs within 0 to 15 seconds). This enables bypass of source address verification, allowing DTLS handshake amplification with spoofed source addresses during this startup window. The affected code is in lib/ssl/src/dtls_server_connection.erl, specifically the dtls_server_connection:initial_hello/3 function. The vulnerability affects OTP versions from 20.0 before 29.0.3, 28.5.0.3, and 27.3.4.14, corresponding to ssl versions from 8.2 before 11.7.3, 11.6.0.3, and 11.2.12.10.

Potential Impact

An attacker capable of observing plaintext ClientHello messages during the initial DTLS server startup window can bypass source address verification by forging valid DTLS cookies. This allows handshake amplification attacks with spoofed source IP addresses, potentially increasing denial-of-service risks. The DTLS cookie is not an authentication mechanism, so the impact is limited to denial-of-service amplification rather than unauthorized access or data compromise.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, consider minimizing exposure during server startup or implementing network-level controls to limit spoofed traffic. Monitor vendor communications for updates on remediation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
EEF
Date Reserved
2026-06-16T10:47:13.915Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 6a46a8b827e9c79719cc4ab5

Added to database: 07/02/2026, 18:06:48 UTC

Last enriched: 07/24/2026, 21:37:16 UTC

Last updated: 08/14/2026, 00:41:13 UTC

Views: 81

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses