Vulnerability Database · Maven · Package report

org.apache.qpid:qpid-broker: vulnerability history, versions and safety

org.apache.qpid:qpid-broker is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 21 releases, from Oct 2018 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.apache.qpid:qpid-broker 10.1.1 i

Updated on 23 Oct 2026

Good news: 10.1.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 10.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 10.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 10.1.1 — unaffected i
  • Vulnerabilities on record 4 over 3 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.qpid:qpid-broker, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
10.1.1 20 Sep 2026 none Apache-2.0 — Details →
10.1.0 31 Jul 2026 none Apache-2.0 — Details →
10.0.1 10 Dec 2025 none Apache-2.0 — Details →
10.0.0 06 Oct 2025 none Apache-2.0 — Details →
9.2.1 24 Feb 2025 none Apache-2.0 — Details →
9.2.0 08 Feb 2024 none Apache-2.0 — Details →
9.1.0 25 Aug 2023 none Apache-2.0 — Details →
9.0.0 14 Nov 2022 none Apache-2.0 — Details →
8.0.6 24 Aug 2021 none Apache-2.0 — Details →
8.0.5 15 Jun 2021 none Apache-2.0 — Details →
8.0.4 15 Feb 2021 none Apache-2.0 — Details →
7.1.12 14 Feb 2021 none Apache-2.0 — Details →
7.1.11 06 Jan 2021 none Apache-2.0 — Details →
8.0.3 05 Jan 2021 none Apache-2.0 — Details →
7.1.10 18 Oct 2020 none Apache-2.0 — Details →
8.0.2 18 Oct 2020 none Apache-2.0 — Details →
8.0.1 15 Sep 2020 none Apache-2.0 — Details →
7.1.9 14 Sep 2020 none Apache-2.0 — Details →
7.0.9 03 Apr 2020 none Apache-2.0 — Details →
8.0.0 04 Mar 2020 none Apache-2.0 — Details →
7.1.8 07 Feb 2020 none Apache-2.0 — Details →
7.1.7 09 Jan 2020 none Apache-2.0 — Details →
7.1.6 02 Dec 2019 none Apache-2.0 — Details →
7.1.5 06 Oct 2019 none Apache-2.0 — Details →
7.0.8 03 Jul 2019 none Apache-2.0 — Details →
7.1.4 03 Jul 2019 none Apache-2.0 — Details →
7.1.3 08 May 2019 none Apache-2.0 — Details →
7.1.2 31 Mar 2019 none Apache-2.0 — Details →
7.0.7 25 Feb 2019 none Apache-2.0 — Details →
7.1.1 25 Feb 2019 none Apache-2.0 — Details →
7.1.0 24 Dec 2018 none Apache-2.0 — Details →
6.1.7 28 Aug 2018 none Apache-2.0 — Details →
7.0.6 19 Jun 2018 none Apache-2.0 — Details →
7.0.5 12 Jun 2018 none Apache-2.0 — Details →
7.0.4 28 May 2018 none Apache-2.0 — Details →
6.1.6 30 Mar 2018 none Apache-2.0 — Details →
7.0.3 30 Mar 2018 none Apache-2.0 — Details →
7.0.2 27 Feb 2018 none Apache-2.0 — Details →
7.0.1 02 Feb 2018 none Apache-2.0 — Details →
6.1.5 17 Nov 2017 none Apache-2.0 — Details →
7.0.0 08 Nov 2017 none Apache-2.0 — Details →
6.0.8 21 Jun 2017 none Apache-2.0 — Details →
6.1.4 21 Jun 2017 H1 Apache-2.0 Yes Details →
6.1.3 25 May 2017 H1 Apache-2.0 Yes Details →
6.0.7 25 May 2017 none Apache-2.0 — Details →
6.1.2 15 Mar 2017 H1 Apache-2.0 Yes Details →
6.0.6 19 Dec 2016 none Apache-2.0 — Details →
6.1.1 19 Dec 2016 H1 Apache-2.0 Yes Details →
6.1.0 10 Nov 2016 H1 Apache-2.0 Yes Details →
6.0.5 24 Oct 2016 H1 Apache-2.0 Yes Details →
6.0.4 28 Jun 2016 H1 Apache-2.0 Yes Details →
6.0.3 19 May 2016 H1 Apache-2.0 Yes Details →
6.0.2 13 Apr 2016 H1 M1 Apache-2.0 Yes Details →
6.0.1 22 Feb 2016 H1 M1 Apache-2.0 Yes Details →
6.0.0 03 Dec 2015 H1 M1 Apache-2.0 Yes Details →
0.32 12 Mar 2015 C1 M1 Apache-2.0 Yes Details →
0.30 11 Sep 2014 C1 M1 Apache-2.0 Yes Details →
0.28 27 May 2014 C1 M1 Apache-2.0 Yes Details →
0.26 02 Feb 2014 C1 M1 Apache-2.0 Yes Details →
0.24 01 Sep 2013 C1 M1 Apache-2.0 Yes Details →
0.22 29 May 2013 C1 M1 Apache-2.0 Yes Details →
0.20 15 Jan 2013 C1 M1 Apache-2.0 Yes Details →
0.18 26 Aug 2012 C1 M1 Apache-2.0 Yes Details →
0.16 13 May 2012 M1 Apache-2.0 Yes Details →
0.14 23 Jan 2012 M1 Apache-2.0 Yes Details →

All 65 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 3
  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.qpid:qpid-broker

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.qpid:qpid-broker

Is org.apache.qpid:qpid-broker safe to use?

Vulert records 4 vulnerabilities for org.apache.qpid:qpid-broker in Maven: 1 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.qpid:qpid-broker's Vulert package health score?

Vulert scores org.apache.qpid:qpid-broker 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.qpid:qpid-broker affected?

No. 10.1.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.qpid:qpid-broker should I use?

10.1.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.qpid:qpid-broker have?

4 vulnerabilities are recorded for org.apache.qpid:qpid-broker in the Maven ecosystem: 1 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.qpid:qpid-broker vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.qpid:qpid-broker in the last 12 months, and the oldest entry in this database dates to 16 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.qpid:qpid-broker are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.qpid:qpid-broker for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.qpid:qpid-broker version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.