CVE-2026-92609: Apache Qpid Broker-J session fixation in HTTP management authentication

CVE-2026-92609 · Severity: critical · CVSS 9.8 · Published 2026-09-25

Apache Qpid Broker-J is a message broker that provides management interfaces for administering message queues. A session fixation vulnerability in the HTTP management authentication allows an attacker to reuse session identifiers to hijack authenticated management sessions, potentially gaining full control of the broker's configuration and operations.

Technologies: Apache Qpid Broker-J. Vendors: Apache.

Quick answers

Is CVE-2026-92609 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-92609 being exploited in the wild.
How severe is CVE-2026-92609?
Critical severity, with a CVSS score of 9.8, published 25 September 2026.
Which products and versions are affected?
Apache Qpid Broker-J through 10.1.0.
Is there a fix for CVE-2026-92609?
A patch was published on 2026-09-25: Fix available in version 10.1.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-92609 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-92609?
Check whether you run Apache Qpid Broker-J at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a session fixation flaw in the HTTP management authentication that fails to invalidate or regenerate session identifiers after successful authentication. An attacker can reuse a retained session identifier to gain unauthorized access to authenticated management sessions without providing valid credentials. This issue affects all versions of Apache Qpid Broker-J through 10.1.0, and is fixed in version 10.1.1.

Affected products

  • Apache Qpid Broker-J through 10.1.0

Timeline

  • 2026-09-25: disclosed
  • 2026-09-25: patched: Fix available in version 10.1.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.