Skip to main content
CVE-2026-103582VulnerabilityPublished

Unbounded memory allocation and missing frame size validation in Apache NMS ActiveMQ (the .NET OpenWire client

Affects apache.nms.activemqSource GCVE Database

0
Compare
Authoritative record:CVE-2026-103582· High

Not known to be exploited : upgrade to 2.3.0 soon.

Data as of 4 Nov 2026, 15:28 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.3.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 4 Nov 2026.

What to do

Upgrade apache.nms.activemq to 2.3.0.

Affected software

ProductAffectedFixed in
NuGetapache.nms.activemqpkg:nuget/apache.nms.activemqOther threatsAffected
  • <2.3.0
Fixed in
  • 2.3.0

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

AI-suggested

Users should upgrade to Apache NMS ActiveMQ version 2.3.0 or later, which includes enforcement of a configurable maximum frame size and validation of frame lengths to prevent excessive memory allocation and related exceptions. No other mitigations are indicated.

Description

Apache NMS ActiveMQ versions before 2.3.0 have a vulnerability in the OpenWire unmarshalling code where frame size and length fields from the network are not properly validated. This allows a malicious or compromised broker, or an attacker intercepting an unencrypted connection, to send crafted frames with oversized or negative lengths. This can cause excessive memory allocation, leading to OutOfMemoryException or uncaught exceptions, resulting in denial of service of the client application. Version 2.3.0 introduces a configurable maximum frame size and proper length validation to mitigate this issue.

References

Community reviews

Loading reviews…