CVE-2026-42792

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% 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, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Improper Handling of Exceptional Conditions vulnerability in Erlang OTP erts (epmd) allows an unauthenticated remote attacker to permanently terminate the Erlang Port Mapper Daemon (epmd) via connection slot exhaustion.

The do_accept function in erts/epmd/src/epmd_srv.c calls epmd_cleanup_exit() when accept(2) returns EMFILE (per-process file descriptor limit reached) or ENFILE (system-wide file descriptor limit reached), rather than treating these as recoverable conditions. An attacker can exhaust epmd's file descriptor slots by holding many TCP connections open while periodically sending a single byte to reset the idle timeout, then causing accept(2) to return EMFILE, which kills the daemon. epmd has no per-source-IP connection cap, making the attack feasible from a single source.

On Debian/Ubuntu default packaging the impact is amplified: the systemd unit inherits a low file descriptor soft limit, and repeated daemon deaths trigger systemd's start-rate-limit, permanently failing both epmd.service and epmd.socket and requiring manual operator intervention to recover.

This issue affects OTP from OTP 17.0 before OTP 29.0.4, OTP 28.5.0.4 and OTP 27.3.4.15.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 27, 2026

Last Modified

August 10, 2026

Advisory Details (5)

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

commit 865d203e4a6a (erlang/otp)

Fix landed in erlang/otp commit 865d203e4a6a — awaiting tagged release

https://github.com/erlang/otp/commit/865d203e4a6a8f44179eced9e1428f9259e4a3bb
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-42792
generic

epmd permanent DoS via EMFILE on accept(2) in erts | Erlang Ecosystem Foundation CNA

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

epmd: Denial-of-service via accept(EMFILE) · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-h6f3-hx58-xhj6

Vendor Advisories for CVE-2026-42792(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 (78 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 23× in last 7d / 91× 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 176 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42792?
CVE-2026-42792 is a high vulnerability published on July 27, 2026. Improper Handling of Exceptional Conditions vulnerability in Erlang OTP erts (epmd) allows an unauthenticated remote attacker to permanently terminate the Erlang Port Mapper Daemon (epmd) via connection slot exhaustion. The doaccept function in erts/epmd/src/epmdsrv.c calls epmdcleanupexit() when…
When was CVE-2026-42792 disclosed?
CVE-2026-42792 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42792 actively exploited?
CVE-2026-42792 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.7% of all scored CVEs.
What is the CVSS score of CVE-2026-42792?
CVE-2026-42792 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42792?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42792, 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-42792

Explore →

Is Your Infrastructure Affected by CVE-2026-42792?

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

Start Free Scan →Browse All CVEs