CVE-2026-67407 Vulnerability Analysis & Exploit Details

CVE-2026-67407
Vulnerability Scoring

7.1
/10
Very High Risk

Highly exploitable, CVE-2026-67407 poses a critical security risk that could lead to severe breaches.

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-67407 Details

Status: Analyzed

Last updated: 🕓 16 Oct 2026, 16:10 UTC
Originally published on: 🕔 25 Sep 2026, 17: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:L/A:N

CVE-2026-67407 Vulnerability Summary

CVE-2026-67407: RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.3.3 and 4.2.9 and 4.1.14 and 4.0.23, Incomplete fix for CVE-2026-44838: escaperegexchar/1 does not escape -, leaving room for an MQTT topic permission bypass. the CVE-2026-44838 fix made expandtopicpermission/2 escape regex metacharacters in expanded topic-permission variables (escaperegex(V)), but escaperegexchar/1 escapes \ ^ $ . | ? + ( ) [ ] { } and omits -. When a topic permission template places {clientid} inside a [...] character class A low-privileged authenticated MQTT user controlling its clientid can broaden topic authorization (read and write) when templates embed {clientid} in a [...] This issue is fixed in versions 4.3.3 and 4.2.9 and 4.1.14 and 4.0.23.

Assessing the Risk of CVE-2026-67407

Access Complexity Graph

The exploitability of CVE-2026-67407 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-67407

CVE-2026-67407 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-67407, 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-67407, 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-67407 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: Low
    Exploiting CVE-2026-67407 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-67407 does not impact system availability.

CVE-2026-67407 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta4:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta4:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta5:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta5:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta6:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.0:beta6:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.20:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.20:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.0.22:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.0.22:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta4:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta4:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta5:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:beta5:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:alpha:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.0:alpha:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.1.11:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.1.11:*:*:*:*:*:*:*
  • 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.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.8:*:*:*:*:*:*:*
  • 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:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-67407: 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-77800 – ManageEngine Key Manager Plus versions before 7151 are vulnerable to a SAML authentication bypass that allows attackers to log in using SAML assert...
  • CVE-2026-77799 – ManageEngine Key Manager Plus versions before 7150 are vulnerable to a Two-Factor Authentication bypass that allows attackers with valid credential...
  • CVE-2026-120971 – RESTEasy's default exception mapper returns an exception's localized message in the HTTP 500 response body when no application exception mapper han...
  • CVE-2026-120578 – The AI Alt Text Generator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.7.0. This is due to th...
  • CVE-2026-120577 – The FluentCart A New Era of eCommerce – Faster, Lighter, and Simpler plugin for WordPress is vulnerable to arbitrary file deletion due to insuffici...