# CVE-2026-93676: Xdg-dbus-proxy: xdg-dbus-proxy: filtering for broadcast messages bypasses path/interface/member checks

> A flaw in xdg-dbus-proxy allows sandboxed Flatpak applications to bypass D-Bus restrictions and intercept sensitive broadcast signals, leading to information disclosure.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** AZL-105116, DEBIAN-CVE-2026-93676, MGASA-2026-0446, UBUNTU-CVE-2026-93676

## What is CVE-2026-93676?

CVE-2026-93676 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 18 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

xdg-dbus-proxy incorrectly filters D-Bus broadcast messages, bypassing configured path, interface, and member restrictions. This allows a sandboxed Flatpak application to intercept broadcast signals on the D-Bus session bus and AT-SPI bus that should be restricted, potentially exposing sensitive information to unauthorized applications.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-93676?


## How do I fix CVE-2026-93676?

Apply the vendor's patch.

## Is CVE-2026-93676 being exploited?

There is no known exploitation of CVE-2026-93676 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93676 and fix it if it is affected.

What it is: CVE-2026-93676 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 18 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93676 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93676/ (Markdown: https://insights.sbomify.com/CVE-2026-93676/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93676
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93676
- OSV: https://osv.dev/vulnerability/CVE-2026-93676

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93676/
Summaries are generated and may contain mistakes; the official description above is the record.