Qpid Broker-J vulnerabilitiesRanked by how likely they are to be used.

Product48 versions
The short answer

Qpid Broker-J is made by Apache. We track 8 published vulnerabilities in it, across 48 versions. None of them is on the list of flaws known to be exploited today. If you run Qpid Broker-J, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Qpid Broker-J vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Qpid Broker-J's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Qpid Broker-J flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 8.9%

    The AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication and consequently perform actions via vectors related to connection state...

    CVSS9.1Published1 Jun 2016
  2. 7.8%

    PlainSaslServer.java in Apache Qpid Java before 6.0.3, when the broker is configured to allow plaintext passwords, allows remote attackers to cause a denial of service (broker termination) via a crafted...

    CVSS5.9Published1 Jun 2016
  3. 6.3%

    The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user authentication.

    CVSS7.5Published15 May 2017
  4. 6.2%

    In Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on different ports one of which is an HTTP port, then the broker can be tricked by a remote...

    CVSS9.8Published1 Dec 2017
  5. 4.4%

    In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame size in AMQP 1.0 frames.

    CVSS7.5Published1 Dec 2017
  6. 3.9%

    A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.0.0-7.0.4 when AMQP protocols 0-8, 0-9 or 0-91 are used to publish messages with size greater than allowed maximum message size limit...

    CVSS7.5Published20 Jun 2018
  7. 3.8%

    A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 which allows an unauthenticated attacker to crash the broker instance by sending specially crafted...

    CVSS7.5Published6 Mar 2019
  8. 2.3%

    A Denial of Service vulnerability was found in Apache Qpid Broker-J 7.0.0 in functionality for authentication of connections for AMQP protocols 0-8, 0-9, 0-91 and 0-10 when PLAIN or XOAUTH2 SASL mechanism is used.

    CVSS5.9Published9 Feb 2018
  9. 0.5%

    A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service.

    CVSS7.5Published25 Sep 2026
  10. 0.5%

    A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service.

    CVSS7.5Published25 Sep 2026
Precursor Intelligence

Running Qpid Broker-J? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Qpid Broker-J, across 48 versions.

None of Qpid Broker-J's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Qpid Broker-J. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.