CVE-2026-49760

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

Stack-based Buffer Overflow vulnerability in Erlang OTP (erl_interface) allows Stack-based Buffer Overflow.

This vulnerability is associated with program file lib/erl_interface/src/misc/ei_printterm.c and program routine ei_s_print_term.

The C function ei_s_print_term uses an internal 2000-character stack buffer to format terms. When called with an encoded Erlang term containing a very large integer (encoded representation exceeding 2000 characters), the buffer overflows. The overflow bytes are restricted to the ASCII values of 0-9 and A-F, which limits exploitation to Denial of Service.

The companion function ei_print_term, which prints directly to a FILE instead of a memory buffer, does not contain this bug.

This issue affects OTP from OTP 17.0 before OTP 29.0.2, OTP 28.5.0.2 and OTP 27.3.4.13, corresponding to erl_interface from 3.7.16 before 5.8.1, 5.7.0.1 and 5.5.2.1.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 24, 2026

Advisory Details (5)

Auto-updated Jun 12, 2026
Patch available. Sources: github_commit, github.
generic

Versions — Erlang System Documentation v29.0.2

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

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-49760
github Patch Available

Stack Buffer Overflow in ei_s_print_term at Very Large Integer · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-xcxj-5pg2-v72j
github_commit

commit 0bef277b2d39 (erlang/otp)

Fix landed in erlang/otp commit 0bef277b2d39 — awaiting tagged release

https://github.com/erlang/otp/commit/0bef277b2d39dc8babb9ceb4f5d0a456f3007111
generic

Stack Buffer Overflow in ei_s_print_term at Very Large Integer | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-49760.html

Vendor Advisories for CVE-2026-49760(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 53× 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-07-27 08:06 UTCEG score recompute
  2. 2026-07-27 08:06 UTCVendor advisory
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 05:19 UTCEG score recompute
  5. 2026-07-26 05:19 UTCVendor advisory
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:18 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 04:58 UTCVendor advisory
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 03:55 UTCVendor advisory
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 01:44 UTCVendor advisory
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 00:28 UTCVendor advisory
Show 62 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 19:52 UTCVendor advisory
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 18:49 UTCVendor advisory
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-08 23:27 UTCVendor advisory
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-07 21:56 UTCVendor advisory
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 21:53 UTCVendor advisory
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 20:50 UTCVendor advisory
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 19:47 UTCVendor advisory
  17. 2026-07-02 18:44 UTCVendor advisory
  18. 2026-07-01 17:42 UTCVendor advisory
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 16:37 UTCVendor advisory
  22. 2026-06-29 15:32 UTCVendor advisory
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:21 UTCVendor advisory
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-27 13:18 UTCVendor advisory
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-26 12:15 UTCVendor advisory
  32. 2026-06-25 13:49 UTCEPSS rescore
  33. 2026-06-25 10:43 UTCVendor advisory
  34. 2026-06-24 14:05 UTCEPSS rescore
  35. 2026-06-24 09:39 UTCVendor advisory
  36. 2026-06-23 21:33 UTCEPSS rescore
  37. 2026-06-23 21:33 UTCEPSS rescore
  38. 2026-06-23 08:30 UTCVendor advisory
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-22 05:55 UTCVendor advisory
  42. 2026-06-21 04:51 UTCVendor advisory
  43. 2026-06-21 01:59 UTCEPSS rescore
  44. 2026-06-21 01:59 UTCEPSS rescore
  45. 2026-06-20 02:53 UTCVendor advisory
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-19 19:26 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-17 17:53 UTCEPSS rescore
  51. 2026-06-16 17:53 UTCEPSS rescore
  52. 2026-06-15 22:37 UTCEG score recompute▼ 1.40
  53. 2026-06-15 19:45 UTCNVD updateCVSS v3 → 5.5
  54. 2026-06-15 17:49 UTCEPSS rescore
  55. 2026-06-15 17:49 UTCEPSS rescore
  56. 2026-06-14 23:18 UTCEPSS rescore
  57. 2026-06-13 23:00 UTCEPSS rescore
  58. 2026-06-12 23:12 UTCEPSS rescore
  59. 2026-06-12 23:12 UTCEPSS rescore
  60. 2026-06-11 14:00 UTCEPSS rescore
  61. 2026-06-10 17:18 UTCEG score recompute
  62. 2026-06-10 17:18 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-49760?
CVE-2026-49760 is a medium vulnerability published on June 10, 2026. Stack-based Buffer Overflow vulnerability in Erlang OTP (erl_interface) allows Stack-based Buffer Overflow. This vulnerability is associated with program file lib/erlinterface/src/misc/eiprintterm.c and program routine eisprint_term. The C function eisprint_term uses an internal 2000-character…
When was CVE-2026-49760 disclosed?
CVE-2026-49760 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49760 actively exploited?
CVE-2026-49760 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-49760?
CVE-2026-49760 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-49760?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49760, 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

Explore the affected products and dependency analysis for CVE-2026-49760

Explore →

Is Your Infrastructure Affected by CVE-2026-49760?

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

Start Free Scan →Browse All CVEs