dbus
Affects dbusSource GCVE Database
Not known to be exploited · CVSS 6.2 Medium.
Data as of 18 Nov 2026, 15:20 UTC
Thin evidence
One scorer or none| 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:HExploitation 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10dbuspkg:deb/ubuntu/dbus?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSdbuspkg:deb/ubuntu/dbus?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSdbuspkg:deb/ubuntu/dbus?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSdbuspkg:deb/ubuntu/dbus?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSdbuspkg:deb/ubuntu/dbus?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSdbuspkg:deb/ubuntu/dbus?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-120749 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-120749 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-120749 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2567978 (opens in a new tab)
- gitlab.freedesktop.org/dbus/dbus/-/merge_requests/565 (opens in a new tab)
- gitlab.freedesktop.org/dbus/dbus/-/merge_requests/592 (opens in a new tab)
- gitlab.freedesktop.org/dbus/dbus/-/work_items/576 (opens in a new tab)