Improper Input Validation vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache…
CVE-2026-49434 is a high-severity improper input validation vulnerability in Apache ActiveMQ Broker 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.8, 6.2.7 as the first without the flaw, so updating Apache ActiveMQ Broker to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.63% chance of exploitation within 30 days, higher than 51% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache ActiveMQ Broker to 5.19.8 or 6.2.7, whichever matches your release line, or a later version.
- Update Apache ActiveMQ to 5.19.8 or 6.2.7, whichever matches your release line, or a later version.
- Update Apache ActiveMQ All to 5.19.8 or 6.2.7, whichever matches your release line, or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache ActiveMQ Broker | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Apache ActiveMQ | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Apache ActiveMQ All | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Activemq | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
| Apache | Activemq Broker | before 5.19.8; 6.0.0 up to, but not including, 6.2.7 | 5.19.8, 6.2.7 |
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
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CISA (ADP).
Official description
Improper Input Validation vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. An attacker that has access to publish or modify entries in LDAP that match the configured searchBase and searchFilter can instantiate denied transports inside the broker JVM. This can be used to fetch an attacker URL and spawn a second BrokerService inside the same JVM. This issue affects Apache ActiveMQ Broker: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ All: before 5.19.8, from 6.0.0 before 6.2.7. Users are recommended to upgrade to version 6.2.7 or 5.19.8, 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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- openwall.com/lists/oss-security/2026/06/29/8Third Party Advisory
Other vulnerabilities in Apache ActiveMQ Broker
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 8.1 High severity
Recent Improper Input Validation vulnerabilities
- 8.1 High severity
- 9.6 Critical severity
- 7.5 High severity
- 9.6 Critical severity
- 9.6 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.