CVE-2026-49759

Stack buffer overflow in SCTP error cause parsing in inet_drv allows remote VM crash

HIGH
8.2
CVSS Score
Published: June 10, 2026 at 02:35 PM UTC
Updated: October 26, 2026 at 11:10 AM UTC
2 products affected across 1 vendorErlang /otpErts

Using OTP by Erlang?

Get instant alerts when new vulnerabilities affect OTP - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

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 27.3.4.13, 28.5.0.2 and 29.0.2, corresponding to erts from 6.0 before 15.2.7.9, 16.4.0.2 and 17.0.2.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

17.0 ≤ v < 27.3.4.1328.0 ≤ v < 28.5.0.229.0 ≤ v < 29.0.217.06.084adefa331c4159d432d22840663c38f155cd4c1
Affected range stops below 27.3.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.5.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 29.0.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3983d495284331c121f600a80bac9fcf4e16381e (unaffected)
16.0 ≤ v < 16.4.0.217.0 ≤ v < 17.0.26.0 ≤ v < 15.2.7.9
Affected range stops below 15.2.7.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.4.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.0.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (8)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHredhat-SADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-121CWE-120

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card