CVE-2026-120749VulnerabilityPublished 6 Nov 2026

CWE-617

Source GCVE Database

Compare

Mentioned vulnerabilities

CVE-2023-34969

Authoritative record:CVE-2026-120749· Medium 6.2

Not known to be exploited · CVSS 6.2 Medium.

Data as of 6 Nov 2026, 10:48 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	6.2

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-r7wg-4x32-8p6v

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10dbus	Affected–	Fixed in–
Red Hat Enterprise Linux 6dbus	Affected–	Fixed in–
Red Hat Enterprise Linux 7dbus	Affected–	Fixed in–
Red Hat Enterprise Linux 8dbus	Affected–	Fixed in–
Red Hat Enterprise Linux 9dbus	Affected–	Fixed in–
Red Hat Hardened Imagesdbus	Affected–	Fixed in–

AI-suggested

The vulnerability can only be triggered if a privileged monitoring process such as dbus-monitor or busctl monitor is active on the same dbus-daemon instance. If no such monitoring process is active, the vulnerable code path is not reached. Since no fixed release is published yet, the primary mitigation is to avoid running privileged monitoring clients unless necessary. Monitor upstream for the release of patches and apply them once available.

Description

A flaw in D-Bus allows an unprivileged local user to cause the dbus-daemon to abort (denial of service) when a privileged monitoring client is attached and a driver-originated broadcast message cannot be delivered. This occurs because driver broadcasts use serial 0, and when delivery fails, an assertion triggers aborting the daemon. This issue is a residual problem from an incomplete fix for CVE-2023-34969 and affects the well-known system bus.

Impact

An unprivileged local user can cause a denial of service by triggering the dbus-daemon to abort if a privileged monitoring client is attached and a driver broadcast message cannot be delivered. This results in a crash of the dbus-daemon, impacting availability. There is no impact on confidentiality or integrity. The attack requires local access and the presence of a privileged monitoring client, which is a privileged operation.

Summary

The vulnerability in D-Bus involves the dbus-daemon aborting when a privileged monitoring client (e.g., dbus-monitor or busctl monitor) is attached and a driver-originated broadcast such as NameOwnerChanged or ActivatableServicesChanged cannot be delivered to a recipient due to deny rules or message queue limits. Driver broadcasts use serial 0, and upon delivery failure, composing the monitor error reply asserts that reply_serial is not zero, causing the daemon to abort. This is an incomplete fix for CVE-2023-34969, which only assigned serials for unicast driver messages. The issue results in a denial of service on the system bus. Upstream vulnerable versions are not yet determined, and no fixed release has been published, though fixes are tracked in upstream merge requests. The vulnerability requires a privileged monitoring process to be active, which limits exposure.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
If the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
Implementation
Consider changing the assertion to some other less "fatal" error. This might not be easy to implement, since other code may be needed to handle the error.
Implementation
Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 10:48 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats