CVE-2026-55737: Heap pointer corruption via signed/unsigned mismatch in LARGE_TUPLE_EXT decoding in erts external term format decoder

Published Jul 27, 2026
·
Updated

Heap pointer corruption via signed/unsigned mismatch in LARGETUPLEEXT decoding in erts external term format decoder

Other sources

Signed to Unsigned Conversion Error and Out-of-bounds Write vulnerability in Erlang OTP erts allows an attacker who can supply a crafted Erlang external term format (ETF) binary to binarytoterm/1 to corrupt the BEAM heap pointer and crash the virtual machine.

When decoding a LARGETUPLEEXT term, the validation pass decodedsize() in erts/emulator/beam/external.c reads the 32-bit arity field as unsigned (getuint32()), while the decode pass decterm() reads the same field as a signed 32-bit integer (getint32()) into an int. An arity wire value of 0x80000000 passes validation as 2147483648 but decodes as -2147483648, so the subsequent hp += n moves the heap allocation pointer backward. Neither pass enforces the runtime tuple-arity limit MAXARITYVAL. The result is an out-of-bounds heap write; in practice the VM detects an impossible heap size and aborts, denying service. The required padding is large when uncompressed but the compressed-ETF envelope shrinks it to a small payload on the wire.

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

MITRE

Affected Software

13 affected componentsFixes available
Open Telecom Platform Erlang OTP (erts external term format decoder)>25.0<=29.0.4
Open Telecom Platform Erlang OTP (erts external term format decoder)>28.5.0.4<=29.0.4
Open Telecom Platform Erlang OTP (erts external term format decoder)>27.3.4.15<=29.0.4
Open Telecom Platform erts<17.0.4
Open Telecom Platform erts<16.4.0.4
Open Telecom Platform erts<15.2.7.11
Microsoft azl3 erlang 26.2.5.21-4<26.2.5.21-3
26.2.5.21-3
Erlang Erlang\/otp>=25.0<27.3.4.15
Erlang Erlang\/otp>=28.0<28.5.0.4
Erlang Erlang\/otp>=29.0<29.0.4
Erlang erts>=13.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 to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.2.5.21-3
  2. Upgrade

    Upgrade Erlang OTP erts (external term format decoder) to a version that resolves this vulnerability.

    Fixed in 29.0.4
  3. Upgrade

    Upgrade Erlang OTP erts (external term format decoder) to a version that resolves this vulnerability.

    Fixed in 28.5.0.4
  4. Upgrade

    Upgrade Erlang OTP erts (external term format decoder) to a version that resolves this vulnerability.

    Fixed in 27.3.4.15
  5. Upgrade

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

    Fixed in 17.0.4
  6. Upgrade

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

    Fixed in 16.4.0.4
  7. Upgrade

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

    Fixed in 15.2.7.11
  8. Compensating control

    If you accept untrusted inputs, ensure attackers cannot reach binary_to_term/1 with crafted Erlang external term format (ETF) binaries (e.g., restrict where binary_to_term/1 is called to trusted data paths).

Event History

Jul 27, 2026
CVE Published
via MITRE·03:13 PM
Data Sourced
via MITRE·03:13 PM
DescriptionWeakness
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 7, 2026
Data Sourced
via Microsoft·07:42 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:42 AM
DescriptionSeverity
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-55737?

The severity of CVE-2026-55737 is rated at 62.

2

How do I fix CVE-2026-55737?

To mitigate CVE-2026-55737, update your Erlang OTP to the latest version that contains the security patch.

3

What software is affected by CVE-2026-55737?

CVE-2026-55737 affects Erlang OTP, specifically the erts component.

4

What kind of attack does CVE-2026-55737 exploit?

CVE-2026-55737 can be exploited by supplying a crafted Erlang external term format binary to binary_to_term/1.

5

What is the impact of CVE-2026-55737?

The impact of CVE-2026-55737 is a potential crash of the BEAM virtual machine due to heap pointer corruption.

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