CVE-2025-30211 | KEX init error results with excessive memory usage

Erlang/OTP is a set of libraries for the Erlang programming language. Prior to versions OTP-27.3.1, 26.2.5.10, and 25.3.2.19, a maliciously formed KEX init message can result with high memory usage. Implementation does not verify RFC specified limits on algorithm names (64 characters) provided in KEX init message. Big KEX init packet may lead to inefficient processing of the error data. As a result, large amount of memory will be allocated for processing malicious data. Versions OTP-27.3.1, OTP-26.2.5.10, and OTP-25.3.2.19 fix the issue. Some workarounds are available. One may set option `parallel_login` to `false` and/or reduce the `max_sessions` option.

Published: 2025-03-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-30211 is rated Moderate Risk (40.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.38%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-30211

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.15% 0.38% +0.23%
2 2026-05-06 0.46% 0.15% -0.31%
3 2026-01-22 — 0.46% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-30211

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-30211

OS Trackers for CVE-2025-30211

vendor priority summary link
debian not yet assigned CVE-2025-30211 not yet assigned priority: Debian including 1 source packages (erlang), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-30211
redhat high — https://access.redhat.com/security/cve/CVE-2025-30211
suse high CVE-2025-30211 severity important: SUSE including 42 source package names (erlang, erlang-22.2.7-150200.3.13.1, …), 79 product×package rows across 19 product lines (SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (19 product lines)): Known Not Affected 53, Fixed 26. https://www.suse.com/security/cve/CVE-2025-30211/
ubuntu medium CVE-2025-30211 medium priority: Ubuntu including 1 source packages (erlang), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): released 7, needs-triage 3. https://ubuntu.com/security/CVE-2025-30211

Affected software / configurations for CVE-2025-30211

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-30211

cvelogic Threat Intelligence