PatchTheCEVqpid broker-j vulnerabilities and fixes
Recent CVEs affecting qpid broker-j, with upgrade or downgrade steps. 7 tracked.
qpid broker-j has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 7. Most recent: 2026-08-05. Highest priority: CVE-2026-68060 (score 50/100).
- CVE-2026-68060 HIGH 7.5 UPGRADE A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to
- CVE-2026-68074 HIGH 7.5 UPGRADE A pre-authentication attacker could leverage unbounded symbol value caching to cause resource exhaustion leadi
- CVE-2026-68073 HIGH 7.5 UPGRADE A pre-authentication attacker could leverage type nesting to cause a StackOverflowError potentially leading to
- CVE-2026-68075 MEDIUM 6.5 UPGRADE An authenticated attacker could exceed the session flow control incoming window potentially leading to denial
- CVE-2026-68077 MEDIUM 6.5 UPGRADE An authenticated attacker can craft a disposition frame with large or illegal ranges causing excessive CPU usa
- CVE-2026-68078 MEDIUM 6.5 UPGRADE It was not possible to govern the maximum number of transfer frames per incoming delivery, enabling an authent
- CVE-2026-68080 MEDIUM 6.5 UPGRADE It was not possible to govern the rate at which the broker would respond to an echo flow, enabling an authenti
FAQ
How do I fix qpid broker-j vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is qpid broker-j being exploited right now?
None of the tracked qpid broker-j CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which qpid broker-j CVE should I patch first?
CVE-2026-68060 currently ranks highest (50/100): A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to.