Skip to main content
VulnerabilityPublished Updated

CVE-2026-54891: Erlang OTP · Improper Enforcement of Message Integrity During Transmission in a Communication Channel

Affects Erlang OTPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium · fixed in 29.0.3 : update Erlang OTP when convenient.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 29.0.3, 28.5.0.3, 27.3.4.14 +4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Upgrade OTP to 29.0.3, 28.5.0.3 or 27.3.4.14; OTP and ssl to 11.7.3, 11.6.0.3 or 11.2.12.10; OTP to 07d2d0e93f6aaf7652a81e8df075fc1728da5e96.

Affected software

ProductAffectedFixed in
ErlangOTPAffected
  • >=29.0 <29.0.3
Fixed in
  • 29.0.3
ErlangOTPAffected
  • >=28.0 <28.5.0.3
Fixed in
  • 28.5.0.3
ErlangOTPAffected
  • >=17.0 <27.3.4.14
Fixed in
  • 27.3.4.14
ErlangOTPAffected
  • >=11.7 <11.7.3
Fixed in
  • 11.7.3
ErlangOTPAffected
  • >=11.3 <11.6.0.3
Fixed in
  • 11.6.0.3
ErlangOTPAffected
  • >=5.3.4 <11.2.12.10
Fixed in
  • 11.2.12.10

CPE configurations (1)

  • cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until then, be aware of the risk of unauthenticated data injection during TLS handshake in affected versions.

Description

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

References

Community reviews

Loading reviews…