Skip to main content
VulnerabilityPublished Updated

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

Affects Apache ActiveMQ NMS AMQP ClientSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.4.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade apache.nms.amqp to 2.4.0.

Affected software

ProductAffectedFixed in
NuGetapache.nms.amqppkg:nuget/apache.nms.amqpOther threatsAffected
  • <2.4.0
Fixed in
  • 2.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation requires upgrading all deployments of Apache ActiveMQ NMS AMQP Client to version 2.4.0 or later, which contains patches that properly restrict deserialization and eliminate the vulnerability. Organizations should audit their messaging infrastructure to identify all instances of the vulnerable client and prioritize patching. As a long-term strategy, projects should migrate away from .NET binary serialization, replacing it with safer serialization formats such as JSON or Protocol Buffers, which are less prone to deserialization attacks. Network segmentation and strict firewall rules should be applied to limit client connections to trusted AMQP servers only. Implementing runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions can help detect and block suspicious deserialization activities. Developers should review and harden deserialization logic, employing allowlists that are rigorously tested against bypass attempts. Monitoring logs for unusual AMQP server responses or client crashes can provide early warning of exploitation attempts. Finally, organizations should stay informed about updates from Apache and .NET regarding serialization security to adapt defenses accordingly.

Description

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.

References

Community reviews

Loading reviews…