CVE-2026-67236 Vulnerability Analysis & Exploit Details

CVE-2026-67236
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2026-67236 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-67236 Details

Status: Analyzed

Last updated: 🕗 15 Oct 2026, 20:24 UTC
Originally published on: 🕓 25 Sep 2026, 16:17 UTC

Time between publication and last update: 20 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVE-2026-67236 Vulnerability Summary

CVE-2026-67236: RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding rather than encryption, an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials; older browsers that treated an absent SameSite attribute as None also sent the cookie cross-site. This issue is fixed in versions 4.2.8 and 4.3.2.

Assessing the Risk of CVE-2026-67236

Access Complexity Graph

The exploitability of CVE-2026-67236 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-67236

CVE-2026-67236 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-67236, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-67236, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-67236 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-67236 poses no threat to data integrity.
  • Availability: None
    CVE-2026-67236 does not impact system availability.

CVE-2026-67236 References

External References

CWE Common Weakness Enumeration

CWE-312

CAPEC Common Attack Pattern Enumeration and Classification

  • Retrieve Embedded Sensitive Data CAPEC-37 An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.

Vulnerable Configurations

  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta4:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta4:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-67236: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-117472 – Psono Server CE && EE versions 4.0.33 through 7.2.3 compared the request path for the bulk-secret-read endpoint with a hard-coded unprefixed path. ...
  • CVE-2026-117471 – Psono Server CE && EE versions 0.1.0 through 7.2.3 accepted a user-controlled host when configuring a personal Duo device and passed it to the Duo ...
  • CVE-2026-117470 – Psono Server CE & EE versions 3.1.0 through 7.2.3 did not consume a stored WebAuthn challenge after assertion verification. An unauthenticated remo...
  • CVE-2026-117469 – Psono Server (CE & EE) versions 1.0.0 through 7.2.3 did not enforce the direction of file-transfer credentials on file-repository operations. An au...
  • CVE-2026-117468 – Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authentica...