Security Resilience

CVE-2026-54891

Erlang\/Otp 17.0 – 27.3.4.14

Published
02 July 2026
Modified
25 October 2026
Patch / advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/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
EPSS Score 0.0014 3th percentile
Risk Priority 29 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-54891 is a medium-severity Improper Enforcement of Message Integrity During Transmission in a Communication Channel (CWE-924) vulnerability in Erlang\/Otp. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) and SC-16 (Transmission of Security and Privacy Attributes) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Improper Enforcement of Message Integrity During Transmission in a Communication Channel vulnerability in Erlang/OTP ssl (tls_gen_connection module) allows a network-positioned attacker to inject unauthenticated plaintext that the TLS client application later treats as authenticated server data. The function tls_gen_connection:handle_protocol_record/3 rejects…

more

APPLICATION_DATA records that arrive in pre-handshake states when the TLS endpoint acts as a server, but does not apply the same check when the endpoint acts as a client. A network-positioned attacker can send plaintext APPLICATION_DATA records to the client during the handshake. The records are buffered and, once the handshake completes successfully, delivered to the application as if they were authenticated post-handshake data. The attacker cannot observe the client's response or steer the connection, so the impact is limited to blind injection of unauthenticated bytes. The injection window is wider for TLS versions prior to TLS 1.3 than for TLS 1.3. This vulnerability is associated with program file lib/ssl/src/tls_gen_connection.erl. TLS 1.3 is affected starting with OTP 22.0, when TLS 1.3 support was added. This issue affects OTP from OTP 17.0 before OTP 27.3.4.14, from OTP 28.0 before OTP 28.5.0.3, and from OTP 29.0 before OTP 29.0.3, corresponding to ssl from 5.3.4 before 11.2.12.10, from 11.3 before 11.6.0.3, and from 11.7 before 11.7.3. Whether OTP before OTP 17.0, corresponding to ssl before 5.3.4, is affected is unknown.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1557.002 ARP Cache Poisoning Credential Access
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices.
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1557.004 Evil Twin Credential Access
Adversaries may host seemingly genuine Wi-Fi access points to deceive users into connecting to malicious networks as a way of supporting follow-on behaviors such as [Network Sniffing](https://attack.
T1684.002 Email Spoofing Stealth
Adversaries may fake, or spoof, a sender’s identity by modifying the value of relevant email headers in order to establish contact with victims under false pretenses.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-55952Same product: Erlang Erlang\/Otp
CVE-2026-54887Same product: Erlang Erlang\/Otp
CVE-2026-55953Same product: Erlang Erlang\/Otp
CVE-2026-48860Same product: Erlang Erlang\/Otp
CVE-2026-55950Same product: Erlang Erlang\/Otp
CVE-2026-32144Same product: Erlang Erlang\/Otp
CVE-2026-42791Same product: Erlang Erlang\/Otp
CVE-2026-42790Same product: Erlang Erlang\/Otp
CVE-2026-58227Same product: Erlang Erlang\/Otp
CVE-2026-42789Same product: Erlang Erlang\/Otp

Affected Assets

erlang
erlang\/otp
17.0 — 27.3.4.14 · 28.0 — 28.5.0.3 · 29.0 — 29.0.3
erlang
erlang\/ssl
5.3.4 — 11.2.12.10 · 11.3 — 11.6.0.3 · 11.7 — 11.7.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Requires protection of integrity for transmitted information, directly stopping the failure to verify messages were unmodified in transit.

Associates integrity-related security attributes with exchanged information, helping ensure modification can be detected during transmission.

Protects session authenticity, which structurally reduces the ability to undetectably modify messages in the channel.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.DS-02 full match
blocks

Directly requires integrity protection (e.g., signatures/hashes) for data-in-transit, which prevents the described weakness while also addressing confidentiality/availability.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

removes

A.8.24 mandates cryptographic protection of integrity for transmitted information (PURPOSE clause names integrity; item (c) names transmitted information; item (f) names approved cryptographic solutions and usage practices). CWE-924 is the absence of message-integrity protection in a communication channel. Applying the clause where it was not applied before requires the developer to implement cryptographic integrity protection (MAC, digital signature, authenticated channel), and the weakness stops being present — the same logic the owner used for A.8.24 removes CWE-311/CWE-312 = full.

blocks

Requires secure information transfer procedures that can include integrity checks.

blocks

A.8.20 item (e) mandates confidentiality and integrity of data passing over networks, and items (k), (l), (n) provide network-layer integrity mechanisms (hardening, segregated admin channels, disabling vulnerable protocols) that block exploitation during the network portion of transit — the same scope logic as the A.8.20 vs CWE-523 anchor. The product-level weakness remains: the receiving endpoint still does not check integrity itself, so if network-layer integrity is terminated at a gateway, bypassed on an alternate path, or absent on a local segment the clause does not reach, the message can still be modified in transit and the product will accept it.

blocks

A.8.21 mandates security features for network services including encryption and connection controls; well implemented, these provide integrity protection over the network service portion of transit, masking the vulnerability during that portion — analogous to A.8.20 vs CWE-523 — but the product-level failure to enforce integrity remains, so end-to-end exploitation is not blocked.

prevents

A.8.28 mandates secure coding principles, threat modelling, secure design and architecture, and prohibits unauthenticated web services — guidance that, well implemented, would catch many instances of missing message integrity at the design and coding stage. But it is a practice control (fallible developers, fallible standards), it does not mandate the specific cryptographic mechanisms for message integrity (that is A.8.24), and third-party components arrive with their integrity choices already made, leaving a nameable remainder.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (4 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-924
  • V-248823 OL 8 must not have the telnet-server package installed. blocks CWE-924
  • V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-924

References