A serious remote code execution (RCE) vulnerability—CVE-2025-32433—has been discovered in the SSH server component of Erlang/OTP, a language and runtime used to build highly scalable and fault-tolerant systems. The flaw allows unauthenticated attackers to execute arbitrary code on vulnerable systems, making it a major concern for organizations that rely on Erlang/OTP directly or through embedded applications.
Even more troubling, public proof-of-concept exploits are now available, and attackers are expected to act fast before organizations have a chance to apply the patches.

What Makes This Vulnerability So Dangerous?
The vulnerability stems from improper handling of SSH protocol messages before authentication. Malformed SSH messages can bypass normal processing rules and trick the server into executing malicious payloads without needing valid credentials. Affected versions include Erlang/OTP releases prior to:
- 27.3.3
- 26.2.5.11
- 25.3.2.20
This issue was disclosed by researchers from Ruhr University Bochum, and proof-of-concept code has been widely shared online, dramatically lowering the barrier to exploitation.
Where Is Erlang/OTP Used?
Erlang/OTP is often quietly embedded in backend systems, meaning many organizations may not even realize they are exposed. It’s widely adopted in telecommunications, messaging platforms, IoT infrastructure, and scalable databases.
Here are a few examples of popular systems and technologies that use Erlang/OTP:
- WhatsApp – Core messaging functionality and real-time communication backend
- RabbitMQ – A widely used message broker for cloud applications
- CouchDB – A distributed database system for high-availability environments
- Riak – A NoSQL key-value database designed for massive scalability
- Ejabberd – An XMPP messaging server used in many chat services
- Open Telecom Platform (OTP) – Used in several telecom-grade solutions
- IoT devices – Various smart routers, controllers, and edge computing systems
Due to its design, Erlang is excellent for systems that demand uptime and concurrency—which means that many systems silently running these services may be vulnerable and mission-critical.
Why It’s Often Missed in Security Audits
Because Erlang/OTP is often bundled within larger software stacks, it doesn’t show up as a standalone service during security scans or audits. Admins may be patching operating systems and application layers while missing the vulnerable SSH server quietly running behind the scenes. This hidden exposure makes CVE-2025-32433 especially worrisome.
The Window for Attack Is Now
With public exploits circulating and the vulnerability freshly patched, the cybersecurity community is warning that attackers will intensify their scans and exploitation attempts before systems are updated.
What to Do Now
To protect your systems:
- Patch immediately: Update Erlang/OTP to a fixed version: 27.3.3, 26.2.5.11, or 25.3.2.20
- Audit all assets: Check software dependencies and embedded services for Erlang usage
- Limit SSH exposure: Temporarily restrict or disable external SSH access to reduce risk
- Monitor your network: Watch for unusual SSH traffic or unexpected behavior from services using Erlang
Summary
CVE-2025-32433 is not just a typical SSH flaw, it’s a reminder that software dependencies matter, especially in complex systems where backend components like Erlang/OTP fly under the radar. This is your opportunity to patch, audit, and reinforce your defenses before attackers exploit this hidden door into your environment.















