Critical Apache ActiveMQ Let Attackers Execute Arbitrary Code
An identified security vulnerability in the Apache ActiveMQ's .NET client library poses a risk of remote code execution. The flaw, referenced as CVE-2025-54539, affects the Apache ActiveMQ NMS AMQP Client when connecting to a compromised AMQP server.
An identified security vulnerability in the Apache ActiveMQ's .NET client library poses a risk of remote code execution. The flaw, referenced as CVE-2025-54539, affects the Apache ActiveMQ NMS AMQP Client when connecting to a compromised AMQP server.
Deserialization Flaw in the NMS AMQP Client
The vulnerability is due to insecure deserialization within the NMS AMQP client library, utilized by .NET applications for communication with AMQP message brokers. Incoming serialized objects are processed without adequate validation.
CVE ID Affected Products CVSS 3.1 Score Impact
CVE-2025-54539 Apache ActiveMQ NMS AMQP Client ≤ 2.3.0 Not available Arbitrary code execution
An identified security vulnerability in the Apache ActiveMQ's .NET client library poses a risk of remote code execution.
Malicious servers can exploit this to execute harmful code on client systems. Although version 2.1.0 introduced allow/deny lists, researchers have bypassed these in certain conditions, affecting all versions up to 2.3.0.
Exploitation of CVE-2025-54539 allows remote code execution, risking data theft or system compromise. The Apache project rates this flaw as Important due to the potential impact on system integrity and availability.
Developers should upgrade to version 2.4.0 or later, where the issue is resolved. Long-term strategies include moving away from .NET binary serialization, as Microsoft plans its deprecation in .NET 9. Adopting safer serialization frameworks and enforcing type checks is recommended.
Security teams should review configurations to ensure connections only to trusted AMQP servers. Network-level controls, such as firewall rules or VPNs, can further mitigate exposure by restricting access to verified endpoints.
Credit for discovering this issue is attributed to the Security Research Team at Endor Labs. More information is available on the Apache ActiveMQ website or the official CVE entry for CVE-2025-54539.
Based on reporting by GBHackers.
