CyberSecBulletin
CVE-2026-59878NVD status: Analyzed

Improper Input Validation vulnerability in Apache ActiveMQ AMQP, Apache ActiveMQ, Apache…

Published Updated By the CyberSecBulletin desk

CVE-2026-59878 is a high-severity improper input validation vulnerability in Apache ActiveMQ AMQP from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 5.19.9, 6.2.8 as the first without the flaw, so updating Apache ActiveMQ AMQP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.78% chance of exploitation within 30 days, higher than 57% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Apache ActiveMQ AMQP to 5.19.9 or 6.2.8, whichever matches your release line, or a later version.
  2. Update Apache ActiveMQ to 5.19.9 or 6.2.8, whichever matches your release line, or a later version.
  3. Update Apache ActiveMQ All to 5.19.9 or 6.2.8, whichever matches your release line, or a later version.
  4. Read the advisory on lists.apache.org for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache ActiveMQ AMQPbefore 5.19.9; 6.0.0 up to, but not including, 6.2.85.19.9, 6.2.8
ApacheApache ActiveMQbefore 5.19.9; 6.0.0 up to, but not including, 6.2.85.19.9, 6.2.8
ApacheApache ActiveMQ Allbefore 5.19.9; 6.0.0 up to, but not including, 6.2.85.19.9, 6.2.8
ApacheActivemqbefore 5.19.9; 6.0.0 up to, but not including, 6.2.85.19.9, 6.2.8
ApacheActivemq Allbefore 5.19.9; 6.0.0 up to, but not including, 6.2.85.19.9, 6.2.8
ApacheActivemq Amqpbefore 5.19.9; 6.0.0 up to, but not including, 6.2.85.19.9, 6.2.8

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CISA (ADP).

Official description

Improper Input Validation vulnerability in Apache ActiveMQ AMQP, Apache ActiveMQ, Apache ActiveMQ All. A remote unauthenticated peer that can reach an exposed AMQP NIO connector can trigger denial-of-service behavior by sending a frame size value. This cause the NIO threads to die and if done rapidly enough can lead to exhaustion of the NIO thread pool denying service to other connections. This issue affects Apache ActiveMQ AMQP: before 5.19.9, from 6.0.0 before 6.2.8; Apache ActiveMQ: before 5.19.9, from 6.0.0 before 6.2.8; Apache ActiveMQ All: before 5.19.9, from 6.0.0 before 6.2.8. Users are recommended to upgrade to version 5.19.9, 6.2.8, or 6.3.0 which fixes the issue.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.