CVE-2026-54891
Erlang\/Otp 17.0 – 27.3.4.14
Raw vector
CVSS: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:XCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2026-41415
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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 1 OS baseline
—
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.
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.
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.
Requires secure information transfer procedures that can include integrity checks.
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.
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.
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