Apache.NMS.AMQP
Apache ActiveMQ NMS.AMQP provides a NMS based client that uses the AMQP v1.0 protocol.
Activity
- Latest release
- 1y ago
- Total releases
- 8
- Cadence
- ~5 months
- Last 12 months
- 0
Details
- First release
- Nov 10, 2019
| Version | Released | |
|---|---|---|
2.4.0
minor
|
2.4.0
minor
Dependencies (3)
|
|
2.3.0
minor
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
2.3.0
minor
Dependencies (3)
|
|
2.2.0
minor
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
2.2.0
minor
Dependencies (3)
|
|
2.1.0
minor
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
2.1.0
minor
Dependencies (3)
|
|
2.0.0
major
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
2.0.0
major
Dependencies (3)
|
|
1.8.2
patch
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
1.8.2
patch
Dependencies (3)
|
|
1.8.1
patch
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
1.8.1
patch
Dependencies (3)
|
|
1.8.0
initial
1 CVE
CVE-2025-54539
GHSA-4mjw-xr5x-prpc
Oct 16, 2025
Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 versions
1.8.0
1.8.1
1.8.2
2.0.0
2.1.0
2.2.0
2.3.0
Fixed in
2.4.0
References Updated Nov 05, 2025 · Source: OSV.dev |
1.8.0
initial
Dependencies (3)
|