CVE-2026-54890: BEAM VM crash via integer underflow in binary_to_term BIT_BINARY_EXT decoding

Published Jul 27, 2026
·
Updated

Integer Underflow (Wrap or Wraparound) vulnerability in erlang otp erlang/otp (erts modules), erlang otp erts (erts modules) allows Forced Integer Overflow, Excessive Allocation. This vulnerability is associated with program files erts/emulator/beam/external.c, emulator/beam/external.c.

The BITBINARYEXT tag (77) handler in the External Term Format (ETF) decoder accepts an encoding with both length and trailing-bits fields set to zero. The subsequent computation of the bitstring size underflows an unsigned integer, producing a value of roughly 2^64 that is then passed as a memory allocation size. The allocator aborts the entire node with a message such as "Cannot allocate 2305843009213693951 bytes of memory (of type binary)".

The crash is a VM-level abort, not an Erlang-level exception. It cannot be intercepted by supervision trees, by try/catch, or by passing the [safe] option to binarytoterm/2 (which only restricts atom creation and does not perform structural validation of binary encodings).

Any application that decodes ETF from untrusted sources via binarytoterm/1,2 or enifbinarytoterm() is exposed. The Erlang distribution protocol also decodes incoming terms through the same code path, but distribution is expected to run on trusted networks per the OTP Secure Coding Guidelines (DSG-011).

This issue affects OTP from OTP 27.0 before OTP 29.0.4, OTP 28.5.0.4 and OTP 27.3.4.15, corresponding to erts from 15.0 before 17.0.4, 16.4.0.4 and 15.2.7.11.

Affected Software

12 affected components
Ericsson Erlang/OTP>27.0<29.0.4
Ericsson Erlang/OTP 28.5>=28.5.0.4<29.0.4
Ericsson Erlang/OTP 27.3>=27.3.4.15<29.0.4
erlang/otp>erts 15.0<17.0.4
erlang/otp>=erts 16.4.0.4<17.0.4
erlang/otp>=erts 15.2.7.11<17.0.4
Erlang Erlang\/otp>=27.0<27.3.4.15
Erlang Erlang\/otp>=28.0<28.5.0.4
Erlang Erlang\/otp>=29.0<29.0.4
Erlang erts>=15.0<15.2.7.11
Erlang erts>=16.0<16.4.0.4
Erlang erts>=17.0<17.0.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade erlang otp (erts) to a version that resolves this vulnerability.

    Fixed in 29.0.4
  2. Upgrade

    Upgrade erlang otp (erts) to a version that resolves this vulnerability.

    Fixed in 28.5.0.4
  3. Upgrade

    Upgrade erlang otp (erts) to a version that resolves this vulnerability.

    Fixed in 27.3.4.15
  4. Upgrade

    Upgrade erts (15.0) to a version that resolves this vulnerability.

    Fixed in 15.2.7.11
  5. Upgrade

    Upgrade erts (16.4.0.4) to a version that resolves this vulnerability.

    Fixed in 16.4.0.4
  6. Upgrade

    Upgrade erts (17.0.4) to a version that resolves this vulnerability.

    Fixed in 17.0.4
  7. Compensating control

    Do not decode ETF (binary_to_term/1, binary_to_term/2, or enif_binary_to_term()) from untrusted sources; ensure distribution protocol traffic (which uses the same ETF decoder path) runs only on trusted networks per OTP Secure Coding Guidelines (DSG-011).

Event History

Jul 27, 2026
CVE Published
via MITRE·03:39 PM
Data Sourced
via MITRE·03:39 PM
DescriptionWeakness
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54890?

CVE-2026-54890 has a severity rating of high, with a CVSS score of 8.2.

2

How do I fix CVE-2026-54890?

To fix CVE-2026-54890, upgrade to the latest patched version of Erlang/OTP provided by the vendor.

3

What software is affected by CVE-2026-54890?

CVE-2026-54890 affects Erlang/OTP versions 27.3 and 28.5.

4

What type of vulnerability is CVE-2026-54890?

CVE-2026-54890 is classified as an Integer Underflow vulnerability that can lead to Forced Integer Overflow.

5

What are the potential impacts of CVE-2026-54890?

The potential impacts of CVE-2026-54890 include application crashes and excessive memory allocation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203