Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-92609 – Session Fixation / Authentication Bypass – Apache Qpid Broker-J ≤ 10.1.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-92609 is a critical session fixation vulnerability (CWE-384) in the HTTP management interface of Apache Qpid Broker-J. The broker fails to renew the HTTP session identifier after a user successfully authenticates to the management console, allowing an attacker who has pre-set or obtained a victim’s session ID to hijack that authenticated session. The issue affects all Apache Qpid Broker-J releases through 10.1.0 and is rated Critical (CVSS 9.8) since it requires no privileges or user interaction and can lead to full compromise of confidentiality, integrity, and availability of the broker.

Technical details

  • Root cause: The Qpid Broker-J HTTP management plugin (org.apache.qpid:qpid-broker-plugins-management-http) does not regenerate or invalidate the session identifier upon successful login, retaining the same session ID that existed prior to authentication.
  • Trigger conditions: An attacker sets or learns a session identifier (e.g., by tricking a victim into using an attacker-supplied session token, a classic session-fixation setup) and waits for the victim to authenticate to the broker’s HTTP management console using that session.
  • Attack vector: Network-based, low complexity, no privileges or user interaction required beyond the victim authenticating with the fixated session ID (AV:N/AC:L/PR:N/UI:N).
  • Impact: Once the victim authenticates, the attacker’s retained session identifier becomes valid for the authenticated management session, granting unauthorized administrative access to the broker’s management interface — enabling manipulation of queues, exchanges, bindings, and message flows, and full read/write/availability impact on the messaging infrastructure.

Affected software

  • Apache Qpid Broker-J: all versions through 10.1.0 (component: qpid-broker-plugins-management-http)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Apache Qpid Broker-J to version 10.1.1, which regenerates the session identifier upon successful authentication to the HTTP management interface.
  • If immediate patching is not possible:
    • Restrict network access to the Qpid Broker-J HTTP management interface to trusted management networks or VPNs only; do not expose it directly to the internet.
    • Enforce HTTPS/TLS for the management interface to reduce the risk of session identifiers being intercepted or predicted.
    • Terminate and rotate any existing management sessions after applying mitigations, and monitor for anomalous authenticated sessions on the management interface.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge