CVE-2026-59250
Buffer overflow in Erlang/OTP megaco flex scanner enabling RCE or DoS.
Is CVE-2026-59250 being exploited?
Not confirmed. CVE-2026-59250 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.78% probability of exploitation in the next 30 days.
How severe is CVE-2026-59250?
CVE-2026-59250 is rated High with a CVSS score of 8.3. 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-59250?
Yes. A fix has been recorded for CVE-2026-59250. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59250 affect?
CVE-2026-59250 affects Erlang/OTP 17.0 - before 29.0.4, megaco 3.17.1 - before 4.9.1 (and listed backports), Nodes configured with {scanner, flex} and reachable Megaco/H.248 port. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59250?
Apply OTP/megaco vendor patches immediately; firewall/restrict Megaco port; restart services after patch.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated buffer overflow via H.248/Megaco message allows arbitrary write/free leading to remote code execution or SIGABRT DoS.
Immediate action required
- affected< 17.0
- affected>= 17.0 and < 27.3.4.15
- affected>= 28.0 and < 28.5.0.4
- affected>= 29.0 and < 29.0.4
- affected< 3.17.1
- affected>= 3.17.1 and < 4.7.2.2
- affected>= 4.8 and < 4.8.3.1
- affected>= 4.9 and < 4.9.1
- affected>= 84adefa331c4159d432d22840663c38f155cd4c1 and < 8704c8f550a11ed5f825e3c011ecb03565b79c4f
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.