dbcve.org
Activemq Nms OpenwireApplication · Apache

CVE-2025-29953

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-18
Fix available
A fix is available. Upgrade to 2.1.1 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
Deserialization of Untrusted Data vulnerability in Apache ActiveMQ NMS OpenWire Client. This issue affects Apache ActiveMQ NMS OpenWire Client before 2.1.1 when performing connections to untrusted servers. Such servers could abuse the unbounded deserialization in the client to provide malicious responses that may eventually cause arbitrary code execution on the client. Version 2.1.0 introduced a allow/denylist feature to restrict deserialization, but this feature could be bypassed. The .NET team has deprecated the built-in .NET binary serialization feature starting with .NET 9 and suggests migrating away from binary serialization. The project is considering to follow suit and drop this part of the NMS API altogether. Users are recommended to upgrade to version 2.1.1, which fixes the issue. We also recommend to migrate away from relying on .NET binary serialization as a hardening method for the future.

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

Deserialization of untrusted data vulnerability in Apache ActiveMQ NMS OpenWire Client versions before 2.1.1 allows malicious servers to exploit unbounded deserialization, potentially executing arbitrary code on the client. The allow/denylist feature introduced in v2.1.0 can be bypassed.

MitigationUpgrade to version 2.1.1 immediately. Additionally, plan migration away from .NET binary serialization as a long-term hardening measure, as .NET 9 has deprecated this feature.

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 OpenwireApplication
Affected:< 2.1.1

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. Locate the NMS OpenWire client library
    Search for Apache.NMS.OpenWire.dll or Apache.NMS.OpenWire.Core.dll in your application directories, or check your NuGet packages.config/project file for Apache.NMS.OpenWire
    Affected if The library is present in your application
  2. Determine the installed version
    Right-click the Apache.NMS.OpenWire.dll file, go to Properties > Details to view the File Version, or check the Version property in your NuGet package reference
    Affected if The version is lower than 2.1.1 (for example, 2.1.0, 2.0.0, or earlier)
  3. Identify if your application uses the OpenWire protocol
    Review your connection factory configuration or code that creates IConnectionFactory - look for instances of NMSOpenWireConnectionFactory or URI schemes starting with activemq:openwire
    Affected if Your application creates connections using the OpenWire protocol to an ActiveMQ broker
  4. Check for deserialization allow/denylist configuration
    Search your configuration files (app.config, web.config) and application code for settings related to SerializationFormatter, TrustedPackages, or DenyDeserializer settings under the Apache.NMS.OpenWire section
    Affected if You rely on the allow/denylist feature (introduced in v2.1.0) to control deserialization, as it can be bypassed in versions before 2.1.1

You are affected if your application uses Apache NMS OpenWire Client version 2.1.0 or earlier and connects to ActiveMQ brokers, especially if you rely on the serialization allow/denylist for protection.

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.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade to version 2.1.1 immediately. Additionally, plan migration away from .NET binary serialization as a long-term hardening measure, as .NET 9 has deprecated this feature.

Recommended fix High confidence

2.1.1

  1. Identify the current version of Apache ActiveMQ NMS OpenWire Client dependency in use (e.g., check .csproj, packages.config, or project references)
  2. Update the NMS OpenWire client package reference to version 2.1.1 or later
  3. Run package restore to fetch the updated dependency
  4. Rebuild the application to ensure the new library is incorporated
  5. Test the application to verify ActiveMQ NMS functionality works correctly with the updated client

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

Fix this in Activemq Nms Openwire Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29953 — 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-29953 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