CVE-2026-93676: xdg-dbus-proxy Information Disclosure Flaw

CVE-2026-93676 Overview

CVE-2026-93676 is an access control weakness in xdg-dbus-proxy, the filtering proxy used by Flatpak to mediate sandboxed application access to the D-Bus session bus and the AT-SPI accessibility bus. The proxy fails to correctly filter D-Bus broadcast messages against its configured path, interface, and member rules. A sandboxed Flatpak application can receive broadcast signals that policy should have blocked, leaking information from other applications on the same bus. The flaw is categorized under CWE-284: Improper Access Control and requires local access with an existing sandboxed context.

Critical Impact
A sandboxed Flatpak application can intercept restricted broadcast signals on the D-Bus session bus and AT-SPI bus, exposing sensitive information from other applications on the user's session.

Affected Products

xdg-dbus-proxy (D-Bus filtering proxy used by Flatpak)
Flatpak sandbox deployments relying on xdg-dbus-proxy for session bus mediation
AT-SPI accessibility bus consumers proxied by xdg-dbus-proxy

Discovery Timeline

2026-09-18 - CVE-2026-93676 published to NVD
2026-09-22 - Last updated in NVD database

Technical Details for CVE-2026-93676

Vulnerability Analysis

xdg-dbus-proxy sits between a sandboxed Flatpak application and the real D-Bus daemon, enforcing an allowlist of paths, interfaces, and members that the sandbox may access. The proxy correctly evaluates unicast method calls and replies but does not apply the same filtering logic to broadcast signal messages. Broadcasts on D-Bus have no specific destination and are delivered to any client that matches a subscription. When the proxy forwards these messages, the configured allowlist is not consulted, so a sandboxed application receives signals it was never authorized to observe.

On a typical Linux desktop, this exposure includes activity on the session bus and the AT-SPI bus. AT-SPI in particular carries accessibility events such as window focus changes, keystroke notifications for assistive technologies, and text updates from user interface elements. A malicious or compromised Flatpak application can passively observe this traffic without triggering the proxy's method-call restrictions.

Root Cause

The root cause is a missing filter path for the D-Bus signal message type in the proxy's rule evaluation. Header fields identifying the sender, path, interface, and member of a broadcast are not matched against the configured policy before the message is delivered to the sandboxed client. The classification [CWE-284] reflects this gap between the intended access control model and the code that implements it.

Attack Vector

Exploitation requires an attacker to already control code running inside a Flatpak sandbox that uses xdg-dbus-proxy with restrictive rules. The attacker's code subscribes to D-Bus signals through the proxy and passively collects broadcasts that policy should have blocked. No privilege escalation, code execution, or bus takeover is achieved; the impact is limited to disclosure of signal contents on the session and AT-SPI buses. No public proof of concept or in-the-wild exploitation has been reported, and the EPSS data reflects a low likelihood of near-term exploitation.

No verified exploit code is publicly available. Consult the Red Hat CVE-2026-93676 Advisory and the OpenWall OSS-Security Discussion for maintainer-provided technical detail.

Detection Methods for CVE-2026-93676

Indicators of Compromise

Flatpak applications subscribing to org.a11y.atspi signals or wildcard signal matches without a legitimate accessibility use case.
Long-lived D-Bus match rules from sandboxed processes targeting interfaces outside their declared permission set.
Presence of xdg-dbus-proxy binaries at versions predating the vendor fix distributed through Flatpak or the host package manager.

Detection Strategies

Audit installed xdg-dbus-proxy versions across Linux endpoints and compare against fixed versions listed in the Red Hat CVE-2026-93676 Advisory.
Inspect Flatpak application manifests for --socket=session-bus, broad --talk-name grants, or accessibility bus access that widens the exposed signal surface.
Correlate process telemetry to identify sandboxed applications making AddMatch calls that reference interfaces outside their sandbox policy.

Monitoring Recommendations

Enable auditd rules for execution of xdg-dbus-proxy and log its command-line arguments to record active filter policies per sandbox.
Monitor D-Bus session bus activity with dbus-monitor in test environments to validate that broadcasts are constrained after patching.
Track Flatpak update events on managed workstations to confirm timely rollout of the fixed xdg-dbus-proxy package.

How to Mitigate CVE-2026-93676

Immediate Actions Required

Update xdg-dbus-proxy to the version identified in the Red Hat CVE-2026-93676 Advisory or the equivalent fixed package from your Linux distribution.
Update the Flatpak runtime and any bundled xdg-dbus-proxy copies shipped inside Flatpak runtimes, not only the host binary.
Review Flatpak permissions with flatpak permissions and revoke session bus or AT-SPI access from applications that do not require it.

Patch Information

Refer to the Red Hat CVE-2026-93676 Advisory and Red Hat Bug Report #2537014 for fixed package versions and downstream backports. The OpenWall OSS-Security Discussion provides upstream context for the fix in xdg-dbus-proxy.

Workarounds

Restrict Flatpak applications to the minimum bus access needed, avoiding --socket=session-bus and --socket=accessibility-bus unless required.
Prefer --talk-name=<specific.service> grants over broad session bus exposure to reduce the volume of signals delivered to the sandbox.
Run untrusted Flatpak applications under a dedicated user account or separate session to isolate broadcast traffic from sensitive workloads.

bash

# Configuration example: restrict a Flatpak app to a single service instead of the full session bus
flatpak override --user \
    --nosocket=session-bus \
    --nosocket=accessibility-bus \
    --talk-name=org.freedesktop.Notifications \
    com.example.UntrustedApp

# Verify effective permissions
flatpak info --show-permissions com.example.UntrustedApp