GHSA-4mjw-xr5x-prpc
Suggest an improvement- Source
- https://github.com/advisories/GHSA-4mjw-xr5x-prpc
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/10/GHSA-4mjw-xr5x-prpc/GHSA-4mjw-xr5x-prpc.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/GHSA-4mjw-xr5x-prpc
- Aliases
-
- CVE-2025-54539
- Published
- 2025-10-16T09:30:24Z
- Modified
- 2025-10-18T08:42:39.243742Z
- Severity
-
- 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- Apache ActiveMQ NMS AMQP Client has a Deserialization of Untrusted Data vulnerability
- Details
-
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.
- Database specific
{ "severity": "CRITICAL", "github_reviewed_at": "2025-10-16T21:05:01Z", "cwe_ids": [ "CWE-502" ], "github_reviewed": true, "nvd_published_at": "2025-10-16T09:15:34Z" }- References
Affected packages
NuGet / Apache.NMS.AMQP
Package
- Name
- Apache.NMS.AMQP
- View open source insights on deps.dev
- Purl
- pkg:nuget/Apache.NMS.AMQP