Erlang OTP up to 29.0.2 TLS Endpoint tls_gen_connection.erl message integrity

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k2.02+

Summaryinfo

A vulnerability has been found in Erlang OTP up to 29.0.2 and classified as critical. This issue affects some unknown processing in the library lib/ssl/src/tls_gen_connection.erl of the component TLS Endpoint. This manipulation causes message integrity. This vulnerability appears as CVE-2026-54891. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Erlang OTP up to 29.0.2. It has been declared as critical. Affected by this vulnerability is an unknown part in the library lib/ssl/src/tls_gen_connection.erl of the component TLS Endpoint. The manipulation with an unknown input leads to a message integrity vulnerability. The CWE definition for the vulnerability is CWE-924. The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission. The impact remains unknown. The summary by CVE is:

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 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. This issue affects OTP from OTP 17.0 before 29.0.3, 28.5.0.3 and 27.3.4.14 corresponding to ssl from 5.3.4 before 11.7.3, 11.6.0.3 and 11.2.12.10. TLS 1.3 is affected starting with OTP 22.0, when TLS 1.3 support was added.

The weakness was presented by Lukas Backström. The advisory is shared at github.com. This vulnerability is known as CVE-2026-54891 since 06/16/2026. The exploitation appears to be easy. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.

Upgrading to version 1.3, 5.3.4, 11.2.12.10, 11.6.0.3, 11.7.3, 17.0, 22.0, 27.3.4.14, 28.5.0.3 or 29.0.3 eliminates this vulnerability. Applying the patch 07d2d0e93f6aaf7652a81e8df075fc1728da5e96 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Message integrity
CWE: CWE-924 / CWE-354 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: OTP 1.3/5.3.4/11.2.12.10/11.6.0.3/11.7.3/17.0/22.0/27.3.4.14/28.5.0.3/29.0.3
Patch: 07d2d0e93f6aaf7652a81e8df075fc1728da5e96

Timelineinfo

06/16/2026 CVE reserved
07/02/2026 +16 days Advisory disclosed
07/02/2026 +0 days VulDB entry created
07/02/2026 +0 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: github.com
Researcher: Lukas Backström
Status: Confirmed

CVE: CVE-2026-54891 (🔒)
GCVE (CVE): GCVE-0-2026-54891
GCVE (VulDB): GCVE-100-375973

Entryinfo

Created: 07/02/2026 19:03
Changes: 07/02/2026 19:03 (57)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!