dbcve.org
Activemq Nms AmqpApplication · Apache

CVE-2025-54539

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 2.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Apache ActiveMQ NMS AMQP Client versions up to 2.3.0 contain a deserialization vulnerability where malicious AMQP servers can craft malicious responses that trigger unsafe deserialization, leading to arbitrary code execution on the client. Although version 2.1.0 introduced allow/deny list protections, these can be bypassed under certain conditions.

MitigationUpgrade to NMS-AMQP version 2.4.0 or later to obtain the security fix, and migrate away from .NET binary serialization as a long-term hardening measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Activemq Nms AmqpApplication
Affected:< 2.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NMS AMQP Client version
    Inspect the project dependencies: check the .csproj file, packages.config, or the loaded assembly version for Apache.NMS.AMQP. If using a compiled binary, use a .NET disassembler or inspect the file properties to find the version metadata.
    Affected if The installed version is prior to 2.4.0 (e.g., 2.3.0, 2.2.0, 2.1.0, etc.)
  2. Verify AMQP client usage in applications
    Search project code for references to Apache.NMS.AMQP namespaces, ConnectionFactory usage, or AMQP connection creation patterns. Check deployed application binaries and dependencies for the presence of Apache.NMS.AMQP.dll.
    Affected if Any application uses the Apache NMS AMQP Client library to connect to AMQP brokers
  3. Confirm allow/deny list configuration
    Search application configuration files (app.config, web.config) and code for SerializationAllowList or SerializationDenyList settings, or any custom deserialization configuration related to NMS AMQP.
    Affected if Allow/deny list is not configured, or the configuration exists but was applied prior to version 2.1.0 when the feature was introduced
  4. Assess broker trust model
    Review the application's AMQP connection configuration to determine whether it connects to trusted or untrusted AMQP servers. Check connection strings or connection factory settings for remote broker addresses.
    Affected if The client connects to untrusted or externally accessible AMQP servers, or the broker is not under the organization's direct control

The environment is affected if the Apache NMS AMQP Client version is below 2.4.0 and the application uses this library to communicate with AMQP servers, particularly untrusted ones.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.0 or later
Fixed in 2.4.0
Interim mitigation

Upgrade to NMS-AMQP version 2.4.0 or later to obtain the security fix, and migrate away from .NET binary serialization as a long-term hardening measure.

Recommended fix High confidence

Version 2.4.0 or later

  1. Upgrade Apache ActiveMQ NMS AMQP Client to version 2.4.0 or later
  2. Verify the upgrade by testing AMQP client connections and functionality
  3. Review and update serialization configurations if previously using allow/deny list mitigations
  4. Plan migration away from .NET binary serialization as a long-term hardening measure
Caveat Review serialization usage as project is moving toward removing .NET binary serialization support

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Activemq Nms Amqp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54539 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data