CVE-2026-59250

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% 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, secondary
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.3Exploit: None knownExposed: 0

A fix is available — apply it.

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, mfs_load_property_groups extracts the attacker-controlled property name (bounded only by the message length) and, when no value follows, formats it into a fixed 512-byte error_msg field of the MfsErlDrvData struct using an unchecked sprintf call. Names longer than roughly 452 bytes overflow into the immediately following struct fields (text_buf, text_ptr, term_spec, term_spec_size, term_spec_index), 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 _FORTIFY_SOURCE 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/megaco_flex_scanner_drv.flex.src and program routines mfs_load_property_groups.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity83% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

July 27, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
Patch available. Sources: github, github_commit.
github_commit

commit 8704c8f550a1 (erlang/otp)

Fix landed in erlang/otp commit 8704c8f550a1 — awaiting tagged release

https://github.com/erlang/otp/commit/8704c8f550a11ed5f825e3c011ecb03565b79c4f
generic

Versions — Erlang System Documentation v29.0.4

https://www.erlang.org/doc/system/versions.html#order-of-versions
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-59250
generic

Megaco flex scanner buffer overflow via oversized property parm name | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-59250.html
github Patch Available

Megaco Flex Scanner Buffer Overflow via Oversized Property Parm Name · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-7xgh-gmgf-q2g7

Vendor Advisories for CVE-2026-59250(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhaterlang27-main-27.3.4.15-0.1.hum12026-07-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
erlang1:25.2.3+dfsg-1 ... 1:29.0~rc3+dfsg-4 (79 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1, 1:27.3.4.1+dfsg-1+deb13u1, 1:27.3.4.1+dfsg-1+deb13u21:27.3.4.1+dfsg-1+deb13u3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (35 versions)1:29.0.4+dfsg-1

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 95× 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 147 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-59250?
CVE-2026-59250 is a high vulnerability published on July 27, 2026. 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…
When was CVE-2026-59250 disclosed?
CVE-2026-59250 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59250 actively exploited?
CVE-2026-59250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59250?
CVE-2026-59250 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-59250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59250, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59250

Explore →

Is Your Infrastructure Affected by CVE-2026-59250?

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