CVE-2025-54539: Apache ActiveMQ NMS AMQP Client: Deserialization of Untrusted Data

Published Oct 15, 2025
·
Updated

A Deserialization of Untrusted Data vulnerability exists in the Apache ActiveMQ NMS AMQP Client.

This issue affects all versions of Apache ActiveMQ NMS AMQP up to and including 2.3.0, when establishing connections to untrusted AMQP servers. Malicious servers could exploit unbounded deserialization logic present in the client to craft responses that may lead to arbitrary code execution on the client side.

Although version 2.1.0 introduced a mechanism to restrict deserialization via allow/deny lists, the protection was found to be bypassable under certain conditions.

In line with Microsoft’s deprecation of binary serialization in .NET 9, the project is evaluating the removal of .NET binary serialization support from the NMS API entirely in future releases.

Mitigation and Recommendations: Users are strongly encouraged to upgrade to version 2.4.0 or later, which resolves the issue. Additionally, projects depending on NMS-AMQP should migrate away from .NET binary serialization as part of a long-term hardening strategy.

Affected Software

3 affected componentsFixes available
Apache Activemq Nms Amqp<=2.3.0
nuget/Apache.NMS.AMQP<2.4.0
2.4.0
Apache Activemq Nms Amqp<2.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade nuget/Apache.NMS.AMQP to a version that resolves this vulnerability.

    Fixed in 2.4.0
  2. Upgrade

    Upgrade Apache ActiveMQ NMS AMQP Client to a version that resolves this vulnerability.

    Fixed in 2.4.0
  3. Compensating control

    Migrate projects depending on NMS-AMQP away from .NET binary serialization as a long-term hardening measure.

Event History

Oct 16, 2025
CVE Published
via MITRE·08:26 AM
Data Sourced
via MITRE·08:26 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:30 AM
Data Sourced
via GitHub·09:30 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-54539?

CVE-2025-54539 is classified as a critical severity vulnerability due to its potential to allow remote code execution.

2

How do I fix CVE-2025-54539?

To mitigate CVE-2025-54539, upgrade to Apache ActiveMQ NMS AMQP version 2.3.1 or later, which addresses the deserialization vulnerability.

3

What versions of Apache ActiveMQ NMS AMQP are affected by CVE-2025-54539?

CVE-2025-54539 affects all versions of Apache ActiveMQ NMS AMQP up to and including version 2.3.0.

4

What types of attacks can be executed through CVE-2025-54539?

Exploitation of CVE-2025-54539 could allow attackers to execute arbitrary code on the client through malicious AMQP server connections.

5

Is CVE-2025-54539 only relevant for specific configurations of Apache ActiveMQ NMS AMQP?

CVE-2025-54539 is relevant for any setup that involves connecting to untrusted AMQP servers, making it a widespread concern across all configurations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203