Vulnerability in xdg-dbus-proxy (UBUNTU-CVE-2026-34080)

Summary

Vulnerability in xdg-dbus-proxy (UBUNTU-CVE-2026-34080). Confidential information can be exposed externally. Mitigation: upgrade to 0.1.7 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-34080 has been found in xdg-dbus-proxy.
Confidential information can be exposed externally.
What to do: upgrade xdg-dbus-proxy to 0.1.7 or later.
If unsure, ask your IT team or search "xdg-dbus-proxy UBUNTU-CVE-2026-34080" on the vendor's site.

UBUNTU-CVE-2026-34080 (xdg-dbus-proxy)
Attack vector: local / no user interaction
Patched: 0.1.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in xdg-dbus-proxy.

📍 Affected scope

Check the vendor advisory for the affected versions of xdg-dbus-proxy.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 0.1.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'xdg-dbus-proxy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'xdg-dbus-proxy' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で xdg-dbus-proxy を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade xdg-dbus-proxy to 0.1.7
```
ステージング環境で 0.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:20.04:LTS xdg-dbus-proxy

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.2-1ubuntu0.1~esm1"}]}]

Ubuntu:22.04:LTS xdg-dbus-proxy

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.3-1ubuntu0.1"}]}]

Ubuntu:24.04:LTS xdg-dbus-proxy

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.5-1ubuntu0.2"}]}]

Ubuntu:25.10 xdg-dbus-proxy

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.6-1ubuntu0.1"}]}]

References

advisory ubuntu.com
advisory ubuntu.com
report ubuntu.com
report cve.org
report github.com