Threats / Erlang / CVE-2025-32433
CVE-2025-32433
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Erlang Erlang/OTP vulnerability
Erlang/OTP SSH server lacks authentication for critical functions, allowing unauthenticated remote code execution through malformed SSH protocol messages.
Verdict
Today item — known-exploited.
An attacker can bypass SSH authentication and execute arbitrary commands on systems running vulnerable Erlang/OTP SSH implementations without valid credentials, leading to complete system compromise.
CISA KEV Yes · 2025-06-095EPSS 0.98594 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
38 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-09).
Probability (EPSS)
EPSS 0.98594 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Erlang, Erlang/OTP. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 54 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious SSH protocol message that exploits missing authentication checks in the SSH server implementation.
Business
Attackers gain initial access to critical infrastructure without requiring valid user credentials or SSH keys.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send the crafted message to trigger execution of arbitrary commands on the target system.
Business
Unauthorized code execution enables attackers to install malware, steal data, or establish persistent access.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate privileges and move laterally across the network using the compromised system as a pivot point.
Business
Breach scope expands beyond the initial system, potentially affecting dependent services and downstream infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05