dbcve.org
Xdg Dbus ProxyApplication · Flatpak

CVE-2026-34080

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 0.1.7 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
xdg-dbus-proxy is a filtering proxy for D-Bus connections. Prior to 0.1.7, a policy parser vulnerability allows bypassing eavesdrop restrictions. The proxy checks for eavesdrop=true in policy rules but fails to handle eavesdrop ='true' (with a space before the equals sign) and similar cases. Clients can intercept D-Bus messages they should not have access to. This vulnerability is fixed in 0.1.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

xdg-dbus-proxy prior to 0.1.7 contains a policy parser vulnerability that allows bypassing eavesdrop restrictions. The parser only correctly handles 'eavesdrop=true' but fails to sanitize variations with whitespace such as 'eavesdrop =\'true\'', allowing clients to intercept D-Bus messages they should not have access to.

MitigationUpgrade xdg-dbus-proxy to version 0.1.7 or later, which contains the fix for proper whitespace handling in the policy parser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xdg Dbus ProxyApplication
Affected:< 0.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check xdg-dbus-proxy version
    Run 'xdg-dbus-proxy --version' or query your package manager (e.g., 'dpkg -l xdg-dbus-proxy' or 'rpm -q xdg-dbus-proxy')
    Affected if The installed version is below 0.1.7 (e.g., 0.1.5, 0.1.6, etc.)
  2. Identify D-Bus policy files in use
    Search for .policy or .conf files in /etc/dbus-1/system.d/, /etc/dbus-1/session.d/, ~/.local/share/, or Flatpak sandbox policy directories
    Affected if Policy files exist that reference 'eavesdrop' settings
  3. Inspect policy files for whitespace before equals
    Grep for 'eavesdrop\s*=' pattern in found policy files, specifically looking for 'eavesdrop =true' or 'eavesdrop = true' with a space before the equals sign
    Affected if Any policy file contains 'eavesdrop =' (with space) instead of 'eavesdrop=' (no space)
  4. Verify Flatpak permissions configuration
    If using Flatpak, check /var/lib/flatpak/.../active/dbus-policy/ directories or examine 'flatpak info --show-permissions' output for any eavesdrop-related entries
    Affected if Flatpak app permissions contain 'eavesdrop' with irregular spacing before the equals sign

You are affected if xdg-dbus-proxy version is below 0.1.7 AND any D-Bus policy files in your environment contain 'eavesdrop =' with whitespace before the equals sign.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.1.7 or later
Fixed in 0.1.7
Interim mitigation

Upgrade xdg-dbus-proxy to version 0.1.7 or later, which contains the fix for proper whitespace handling in the policy parser.

Recommended fix High confidence

0.1.7

  1. 1. Check the currently installed version of xdg-dbus-proxy using your system's package manager or by running 'xdg-dbus-proxy --version'
  2. 2. Upgrade xdg-dbus-proxy to version 0.1.7 or later. For Debian/Ubuntu systems, run: sudo apt update && sudo apt install xdg-dbus-proxy
  3. 3. For other distributions, use the appropriate package manager or build from source by cloning the repository and checking out tag version 0.1.7
  4. 4. Verify the upgrade was successful by running 'xdg-dbus-proxy --version' and confirming the version is 0.1.7 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xdg Dbus Proxy Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34080 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data