CVE-2026-49759

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% 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
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: 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 erts (inet_drv) allows an unauthenticated remote attacker to crash the BEAM VM by sending a crafted SCTP ERROR chunk.

The sctp_parse_error_chunk function in erts/emulator/drivers/common/inet_drv.c parses SCTP ERROR chunks and writes cause codes into a fixed-size stack-allocated ErlDrvTermData spec[] array without checking bounds. A remote attacker who has established an SCTP association to a listening port can send a single crafted SCTP ERROR chunk containing enough cause codes to overflow the stack buffer, crashing the VM. The attacker can only write 16-bit values interleaved with a fixed tag, so the overflow does not provide a controlled return address, limiting exploitation to Denial of Service.

A crafted SCTP ERROR chunk may also leak bits and pieces of Erlang VM memory into the received error packet observed by the Erlang process. Such data is already readable by the user running the Erlang VM, so the disclosure scope is limited.

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 erts from 6.0 before 17.0.2, 16.4.0.2 and 15.2.7.9.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 24, 2026

Advisory Details (5)

Auto-updated Jun 10, 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-49759
github Patch Available

Unbounded Stack Buffer Overflow in SCTP Error Cause Parsing in inet_drv · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-6f4f-chj5-5g97
github_commit

commit 3983d4952843 (erlang/otp)

Fix landed in erlang/otp commit 3983d4952843 — awaiting tagged release

https://github.com/erlang/otp/commit/3983d495284331c121f600a80bac9fcf4e16381e
generic

Stack buffer overflow in SCTP error cause parsing in inet_drv allows remote VM crash | Erlang Ecosystem Foundation CNA

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

Vendor Advisories for CVE-2026-49759(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 68× 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.

Showing the most recent 100 of 112 total refreshes for this CVE.

  1. 2026-07-28 02:18 UTCEG score recompute
  2. 2026-07-28 02:18 UTCVendor advisory
  3. 2026-07-27 10:04 UTCVendor advisory
  4. 2026-07-26 21:00 UTCEG score recompute
  5. 2026-07-26 21:00 UTCVendor advisory
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 05:19 UTCEG score recompute
  8. 2026-07-26 05:19 UTCVendor advisory
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-24 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:18 UTCEG score recompute
  13. 2026-07-22 14:08 UTCEPSS rescore
  14. 2026-07-21 15:25 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-15 22:15 UTCVendor advisory
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-14 16:01 UTCVendor advisory
Show 75 more
  1. 2026-07-14 02:54 UTCVendor advisory
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 00:30 UTCVendor advisory
  5. 2026-07-12 10:02 UTCVendor advisory
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 20:58 UTCVendor advisory
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 07:53 UTCVendor advisory
  10. 2026-07-10 18:49 UTCVendor advisory
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 13:38 UTCVendor advisory
  13. 2026-07-09 00:14 UTCVendor advisory
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 10:59 UTCVendor advisory
  16. 2026-07-07 21:56 UTCVendor advisory
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:59 UTCVendor advisory
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 13:54 UTCVendor advisory
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-05 00:50 UTCVendor advisory
  24. 2026-07-04 11:45 UTCVendor advisory
  25. 2026-07-04 06:31 UTCEPSS rescore
  26. 2026-07-03 21:05 UTCVendor advisory
  27. 2026-07-03 08:01 UTCVendor advisory
  28. 2026-07-02 18:00 UTCVendor advisory
  29. 2026-07-02 04:53 UTCVendor advisory
  30. 2026-07-01 15:49 UTCVendor advisory
  31. 2026-07-01 15:07 UTCEPSS rescore
  32. 2026-07-01 02:45 UTCVendor advisory
  33. 2026-06-30 23:22 UTCEPSS rescore
  34. 2026-06-30 13:41 UTCVendor advisory
  35. 2026-06-29 22:29 UTCVendor advisory
  36. 2026-06-29 14:06 UTCEPSS rescore
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-29 09:25 UTCVendor advisory
  39. 2026-06-28 20:21 UTCVendor advisory
  40. 2026-06-28 14:07 UTCEPSS rescore
  41. 2026-06-28 07:16 UTCVendor advisory
  42. 2026-06-28 04:56 UTCEPSS rescore
  43. 2026-06-28 04:56 UTCEPSS rescore
  44. 2026-06-27 18:12 UTCVendor advisory
  45. 2026-06-27 05:07 UTCVendor advisory
  46. 2026-06-27 03:08 UTCEPSS rescore
  47. 2026-06-26 15:50 UTCVendor advisory
  48. 2026-06-26 02:43 UTCVendor advisory
  49. 2026-06-25 13:49 UTCEPSS rescore
  50. 2026-06-25 13:38 UTCVendor advisory
  51. 2026-06-25 00:33 UTCVendor advisory
  52. 2026-06-24 14:05 UTCEPSS rescore
  53. 2026-06-24 11:28 UTCVendor advisory
  54. 2026-06-23 22:21 UTCVendor advisory
  55. 2026-06-23 21:33 UTCEPSS rescore
  56. 2026-06-23 21:33 UTCEPSS rescore
  57. 2026-06-23 08:30 UTCVendor advisory
  58. 2026-06-22 18:20 UTCVendor advisory
  59. 2026-06-22 14:25 UTCEPSS rescore
  60. 2026-06-22 14:25 UTCEPSS rescore
  61. 2026-06-22 04:17 UTCVendor advisory
  62. 2026-06-21 15:11 UTCVendor advisory
  63. 2026-06-21 14:56 UTCEPSS rescore
  64. 2026-06-21 14:56 UTCEPSS rescore
  65. 2026-06-21 01:59 UTCEPSS rescore
  66. 2026-06-21 01:59 UTCEPSS rescore
  67. 2026-06-21 01:50 UTCVendor advisory
  68. 2026-06-20 12:45 UTCVendor advisory
  69. 2026-06-19 23:41 UTCVendor advisory
  70. 2026-06-19 19:26 UTCEPSS rescore
  71. 2026-06-19 19:26 UTCEPSS rescore
  72. 2026-06-19 10:37 UTCVendor advisory
  73. 2026-06-18 17:52 UTCEPSS rescore
  74. 2026-06-18 17:52 UTCEPSS rescore
  75. 2026-06-17 17:53 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-49759?
CVE-2026-49759 is a high vulnerability published on June 10, 2026. Stack-based Buffer Overflow vulnerability in Erlang OTP erts (inet_drv) allows an unauthenticated remote attacker to crash the BEAM VM by sending a crafted SCTP ERROR chunk. The sctpparseerrorchunk function in erts/emulator/drivers/common/inetdrv.c parses SCTP ERROR chunks and writes cause codes…
When was CVE-2026-49759 disclosed?
CVE-2026-49759 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-49759 actively exploited?
CVE-2026-49759 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 60.3% of all scored CVEs.
What is the CVSS score of CVE-2026-49759?
CVE-2026-49759 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-49759?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49759, 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-49759

Explore →

Is Your Infrastructure Affected by CVE-2026-49759?

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