Skip to content
Threat Brief

← All advisories

CVE-2026-54890

High 8.2No known exploitationFix available

BEAM VM crash via integer underflow in binary_to_term BIT_BINARY_EXT decoding

Record last updated

CVSS score

8.2

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 40% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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 BIT_BINARY_EXT 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 binary_to_term/2 (which only restricts atom creation and does not perform structural validation of binary encodings). Any application that decodes ETF from untrusted sources via binary_to_term/1,2 or enif_binary_to_term() 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 27.3.4.15, OTP 28.5.0.4, and OTP 29.0.4, corresponding to erts from 15.0 before 15.2.7.11, 16.4.0.4, and 17.0.4.

Weakness: CWE-191, CWE-789, CWE-1284

Patching and mitigation

Patch status
Fix available (source: NVD (reference tagged Patch))
Fix documented (source date)
Mitigation
Do not call binary_to_term/1,2 or enif_binary_to_term() on data from untrusted sources. The OTP Secure Coding Guidelines (DSG-011) recommend avoiding these functions altogether on untrusted input and using an alternative serialization format (for example JSON or Protocol Buffers) instead. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ErlangOTPfrom 24ef4cbaeda9b9c26682cba75f2f15b0c58722aa before dc1bf9344c0ce62717cf60866590cea0242780fddc1bf9344c0ce62717cf60866590cea0242780fdCVE Program
ErlangOTP15.0Not documentedCVE Program
ErlangOTP27.0Not documentedCVE Program
erlangerlang/otpfrom 27.0 before 27.3.4.1527.3.4.15NIST NVD
erlangerlang/otpfrom 28.0 before 28.5.0.428.5.0.4NIST NVD
erlangerlang/otpfrom 29.0 before 29.0.429.0.4NIST NVD
erlangertsfrom 15.0 before 15.2.7.1115.2.7.11NIST NVD
erlangertsfrom 16.0 before 16.4.0.416.4.0.4NIST NVD
erlangertsfrom 17.0 before 17.0.417.0.4NIST NVD

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by NVD (reference tagged Patch)

    Source: NVD (reference tagged Patch) (opens in a new tab)

Vendor guidance and references