CVE-2026-55737

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 binary_to_term/1 to corrupt the BEAM heap pointer and crash the virtual machine.

When decoding a LARGE_TUPLE_EXT term, the validation pass decoded_size() in erts/emulator/beam/external.c reads the 32-bit arity field as unsigned (get_uint32()), while the decode pass dec_term() reads the same field as a signed 32-bit integer (get_int32()) 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 MAX_ARITYVAL. 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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 27, 2026

Last Modified

August 10, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
Patch available. Sources: github, github_commit.
github_commit

commit c5210b42a9d3 (erlang/otp)

Fix landed in erlang/otp commit c5210b42a9d3 — awaiting tagged release

https://github.com/erlang/otp/commit/c5210b42a9d3d96f3d25601942ce8122be0f3761
generic

Versions — Erlang System Documentation v29.0.4

https://www.erlang.org/doc/system/versions.html#order-of-versions
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-55737
generic

Heap pointer corruption via signed/unsigned mismatch in LARGE_TUPLE_EXT decoding in erts external term format decoder | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-55737.html
github Patch Available

Heap Pointer Corruption via signed/unsigned Mismatch in LARGE_TUPLE_EXT Decoding (binary_to_term/1) · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-446w-268v-9462

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
erlang1:25.2.3+dfsg-1 ... 1:29.0~rc3+dfsg-4 (78 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (38 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (35 versions)1:29.0.4+dfsg-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 21× in last 7d / 85× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 10:45 UTCVendor advisory
  3. 2026-08-24 21:49 UTCEG score recompute
  4. 2026-08-24 21:49 UTCVendor advisory
  5. 2026-08-24 08:55 UTCVendor advisory
  6. 2026-08-23 20:00 UTCVendor advisory
  7. 2026-08-23 07:05 UTCEG score recompute
  8. 2026-08-23 07:05 UTCVendor advisory
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 18:10 UTCVendor advisory
  11. 2026-08-22 05:14 UTCEG score recompute
  12. 2026-08-22 05:14 UTCVendor advisory
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 03:23 UTCEG score recompute
  15. 2026-08-21 03:23 UTCVendor advisory
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 14:28 UTCVendor advisory
  18. 2026-08-20 00:12 UTCEG score recompute
  19. 2026-08-20 00:12 UTCVendor advisory
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 11:16 UTCVendor advisory
  22. 2026-08-18 22:16 UTCEG score recompute
  23. 2026-08-18 22:16 UTCVendor advisory
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 20:22 UTCEG score recompute
Show 60 more
  1. 2026-08-17 20:22 UTCVendor advisory
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 07:27 UTCVendor advisory
  4. 2026-08-16 18:33 UTCEG score recompute
  5. 2026-08-16 18:33 UTCVendor advisory
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 05:38 UTCEG score recompute
  8. 2026-08-16 05:38 UTCVendor advisory
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 16:44 UTCVendor advisory
  11. 2026-08-15 03:49 UTCEG score recompute
  12. 2026-08-15 03:49 UTCVendor advisory
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 14:54 UTCVendor advisory
  15. 2026-08-14 01:59 UTCEG score recompute
  16. 2026-08-14 01:59 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 13:05 UTCVendor advisory
  19. 2026-08-13 00:10 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-12 11:16 UTCVendor advisory
  22. 2026-08-11 22:21 UTCEG score recompute
  23. 2026-08-11 22:21 UTCVendor advisory
  24. 2026-08-11 09:26 UTCEG score recompute
  25. 2026-08-11 09:26 UTCVendor advisory
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 20:31 UTCEG score recompute 2.40
  28. 2026-08-10 20:29 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  29. 2026-08-10 05:58 UTCEG score recompute
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 07:05 UTCEG score recompute
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 08:12 UTCEG score recompute
  34. 2026-08-08 08:12 UTCVendor advisory
  35. 2026-08-07 09:18 UTCEG score recompute
  36. 2026-08-06 13:47 UTCEPSS rescore
  37. 2026-08-06 10:25 UTCEG score recompute
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 11:31 UTCEG score recompute
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 12:37 UTCEG score recompute
  42. 2026-08-04 10:39 UTCEPSS rescore
  43. 2026-08-03 12:51 UTCEG score recompute
  44. 2026-08-03 10:36 UTCEPSS rescore
  45. 2026-08-02 13:47 UTCEG score recompute
  46. 2026-08-02 02:27 UTCEPSS rescore
  47. 2026-08-01 14:54 UTCEG score recompute
  48. 2026-08-01 04:16 UTCEPSS rescore
  49. 2026-07-30 17:05 UTCEG score recompute
  50. 2026-07-30 16:28 UTCEPSS rescore
  51. 2026-07-30 08:03 UTCEG score recompute
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-29 09:09 UTCEG score recompute
  54. 2026-07-28 15:37 UTCEPSS rescore
  55. 2026-07-28 10:16 UTCEG score recompute
  56. 2026-07-27 19:30 UTCEG score recompute
  57. 2026-07-27 19:06 UTCEG score recompute
  58. 2026-07-27 16:24 UTCEG score recompute
  59. 2026-07-27 15:31 UTCEG score recompute
  60. 2026-07-27 15:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55737?
CVE-2026-55737 is a high vulnerability published on July 27, 2026. 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…
When was CVE-2026-55737 disclosed?
CVE-2026-55737 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55737 actively exploited?
CVE-2026-55737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.2% of all scored CVEs.
What is the CVSS score of CVE-2026-55737?
CVE-2026-55737 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55737, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55737

Explore →

Is Your Infrastructure Affected by CVE-2026-55737?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.