A flaw was found in dbus-broker. When the process file-descriptor limit is reached, EMFILE/ENFILE errors during peer setup (notably SO_PEERPIDFD) are handled as fatal failures, causing the broker to exit. A local attacker who can open many connections to the user session bus can trigger this and deny service to the desktop session. Flatpak applications can reach the host session bus through the dbus proxy.
CVE-2026-16730
Score 5.5 from GitHub Security Advisory published 2026-07-24. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 24, 2026
Advisory Details (3)
Auto-updated Jul 24, 2026dbus-broker-launch shuts down when hitting user soft fd limit · Issue #435 · bus1/dbus-broker · GitHub
https://github.com/bus1/dbus-broker/issues/4352506348 – (CVE-2026-16730) CVE-2026-16730 dbus-broker: dbus-broker: session bus denial of service via EMFILE during peer setup
https://bugzilla.redhat.com/show_bug.cgi?id=2506348Vendor Advisories for CVE-2026-16730(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 05:29 UTCEG score recompute
- 2026-07-27 05:29 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:03 UTCEG score recompute
- 2026-07-26 03:03 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 12:02 UTCEG score recompute
- 2026-07-24 12:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-755
- CVE-2009-5043EG 9.8CRITICAL
- CVE-2019-17195EG 9.8EPSS p95CRITICAL
- CVE-2019-14431EG 9.8CRITICAL
- CVE-2019-12815EG 9.8EPSS p99CRITICAL
- CVE-2018-19991EG 9.8CRITICAL
- CVE-2017-2877EG 9.8CRITICAL
- CVE-2017-5638EG 9.8 KEVEPSS p100CRITICAL
- CVE-2018-0155NVD 8.6EG 9.0 KEVEPSS p94CRITICAL
- CVE-2019-14287EG 8.9EPSS p99HIGH
- CVE-2019-14378EG 8.8EPSS p97HIGH
Frequently asked(5)
What is CVE-2026-16730?
When was CVE-2026-16730 disclosed?
Is CVE-2026-16730 actively exploited?
What is the CVSS score of CVE-2026-16730?
How do I remediate CVE-2026-16730?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16730
Is Your Infrastructure Affected by CVE-2026-16730?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.