Skip to content
Infrastructure

CVE-2026-49759

8.8
High
EPSS 0.50%Patch availableJun 11, 2026

Stack-based buffer overflow in Erlang OTP erts inet_drv; unauthenticated remote crash via SCTP ERROR chunk.

common questions

Is CVE-2026-49759 being exploited?

Not confirmed. CVE-2026-49759 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.

How severe is CVE-2026-49759?

CVE-2026-49759 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49759?

Yes. A fix has been recorded for CVE-2026-49759. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49759 affect?

CVE-2026-49759 affects Erlang/OTP runtime (erts) versions: OTP 17.0.x before 27.3.4.13; 28.5.0.2; 29.0.2; erts 6.0 before 15.2.7.9; 16.4.0.2; 17.0.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49759?

Upgrade to fixed OTP/erts versions.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Erlang/OTP runtime (erts) versions: OTP 17.0.x before 27.3.4.13; 28.5.0.2; 29.0.2; erts 6.0 before 15.2.7.9; 16.4.0.2; 17.0.2
impact

Remote crash of BEAM VM via crafted SCTP ERROR chunk; DoS; potential memory leakage; no RCE.

action required

Patch when possible

affected versions
Erlang OTP
  • affected>= 6.0 and < *
  • affected>= 17.0 and < *
  • affected>= 84adefa331c4159d432d22840663c38f155cd4c1 and < 3983d495284331c121f600a80bac9fcf4e16381e

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free