Skip to main content
VulnerabilityPublished Updated

CVE-2026-93575: Red Hat AMQ Broker 7 · CWE-1035

Affects Red Hat AMQ Broker 7Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 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 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat AMQ Broker 7Affected–Fixed in–
Red HatRed Hat build of Apache Camel for Spring Boot 4Affected–Fixed in–
Red HatRed Hat Fuse 7Affected–Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform 7Affected–Fixed in–
Red HatRed Hat Single Sign-On 7Affected–Fixed in–

AI-suggested

Until a patch is applied, consider network-level controls to restrict unauthenticated MQTT CONNECT packets from untrusted sources.

Description

A flaw was found in Netty's MqttDecoder. An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted MQTT CONNECT packet. The decoder fails to properly validate the 'Properties Length' against the 'Remaining Length', allowing an attacker to bypass size limits. This leads to excessive memory and CPU consumption, resulting in a denial of service (DoS) due to an OutOfMemoryError.

References

Community reviews

Loading reviews…