Skip to content
Fencer Vulns
high 7.1

CVE-2026-39959 json

Tmds.DBus: malicious D-Bus peers can spoof signals, exhaust file descriptor resources, and cause denial of service

published 2026-04-08 7 mo ago modified 2026-10-26 13 d ago also GHSA-xrw6-gwf8-vvr9 , EUVD-2026-20964

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

Tmds.DBus provides .NET libraries for working with D-Bus from .NET. Tmds.DBus and Tmds.DBus.Protocol are vulnerable to malicious D-Bus peers. A peer on the same bus can spoof signals by impersonating the owner of a well-known name, exhaust system resources or cause file descriptor spillover by sending messages with an excessive number of Unix file descriptors, and crash the application by sending malformed message bodies that cause unhandled exceptions on the SynchronizationContext. This vulnerability is fixed in Tmds.DBus 0.92.0 and Tmds.DBus.Protocol 0.92.0 and 0.21.3.

Patch / fix

  • nuget Tmds.DBus 0.92.0
  • nuget Tmds.DBus.Protocol 0.21.3, 0.92.0

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
GitHub 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
nuget Tmds.DBus
<0.92.0
0.92.0
nuget Tmds.DBus.Protocol
<0.21.3
>=0.22.0, <0.92.0
0.21.3
0.92.0

Affected products

  • tmds Tmds.DBus
  • tmds Tmds.DBus.Protocol

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling
  • CWE-290 Authentication Bypass by Spoofing
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.