CVE-2026-59250: Megaco flex scanner buffer overflow via oversized property parm name
Classic buffer overflow in the Erlang/OTP megaco flex scanner C driver allows a remote unauthenticated attacker to corrupt the driver's memory (and potentially achieve remote code execution or a denial-of-service crash) by sending a single text-encoded H.248/Megaco message containing an oversized property parm name.
When tokenizing a Local/Remote descriptor, mfsloadpropertygroups extracts the attacker-controlled property name (bounded only by the message length) and, when no value follows, formats it into a fixed 512-byte errormsg field of the MfsErlDrvData struct using an unchecked sprintf call. Names longer than roughly 452 bytes overflow into the immediately following struct fields (textbuf, textptr, termspec, termspecsize, termspecindex), overwriting live pointers and counters with attacker-chosen bytes. Subsequent scanner code writes and frees through the corrupted pointers, producing arbitrary write and arbitrary free primitives inside the BEAM VM process, which can be leveraged for remote code execution. On builds compiled with FORTIFYSOURCE the overflow is detected at runtime and terminates the process with SIGABRT, resulting in denial of service.
The overflow occurs in the flex scanner before any grammar or Megaco-level authentication processing, so exploitation requires only network reachability to the megaco transport port on a node configured with {scanner, flex}.
This vulnerability is associated with program files lib/megaco/src/flex/megacoflexscannerdrv.flex.src and program routines mfsloadpropertygroups.
This issue affects OTP from OTP 17.0 before OTP 27.3.4.15, from OTP 28.0 before OTP 28.5.0.4, and from OTP 29.0 before OTP 29.0.4, corresponding to megaco from 3.17.1 before 4.7.2.2, from 4.8 before 4.8.3.1, and from 4.9 before 4.9.1. Whether OTP before OTP 17.0, corresponding to megaco before 3.17.1, is affected is unknown.
Other sources
Megaco flex scanner buffer overflow via oversized property parm name
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 26.2.5.21-5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 27.3.4.15 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 28.5.0.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 29.0.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 4.7.2.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 4.8.3.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 4.9.1 - Compensating control
Ensure BEAM node only exposes the megaco transport port (configured with {scanner, flex}) to trusted network sources, since exploitation requires only network reachability before any grammar or Megaco-level authentication processing.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59250?
The severity of CVE-2026-59250 is high, with a CVSS score of 8.3.
How do I fix CVE-2026-59250?
To fix CVE-2026-59250, update the Erlang/OTP to the latest version that addresses the buffer overflow issue.
What type of vulnerability is CVE-2026-59250?
CVE-2026-59250 is classified as a buffer overflow vulnerability.
What is the impact of CVE-2026-59250?
CVE-2026-59250 can lead to remote code execution or a denial-of-service crash.
Who can exploit CVE-2026-59250?
CVE-2026-59250 can be exploited by a remote unauthenticated attacker.