CVE Intelligence
Skip to main content
highAuth Bypasspublic exploit

CVE-2026-94422

CVE-2026-94422 — xdg-dbus-proxy: message filtering bypass via reply serial allows sandbox escape

An incorrect implementation of message filtering in xdg-dbus-proxy versions before 0.1.9 allows an attacker to bypass the intended message filtering on the D-Bus session bus by setting a reply serial number on non-reply messages. A malicious or compromised Flatpak app could use this to achieve arbitrary code execution outside its sandbox. xdg-dbus-proxy was designed to be part of the sandbox boundary for Flatpak, but it is released as a separate project and is sometimes used by other app frameworks such as Firejail.

Published Updated Sources: NVD, flatpak (CNA), GitHub, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

flatpak

4 products listed

CVSS base

8.8

high · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade xdg-dbus-proxy to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2026-94422

fixed0affected2not affected0

workaround: Avoid running untrusted Flatpak apps and avoid running untrusted apps via other frameworks that use xdg-dbus-proxy.

none_available: Affected

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
flatpakxdg-dbus-proxy0 to < 0.1.9Vulnerable
FedoraFedora0 to < 0.1.9Vulnerable
Red HatRed Hat Enterprise Linux 9—Vulnerable
Red HatRed Hat Enterprise Linux 10—Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1high2.85.9Red Hat (CNA), flatpak (CNA), Red Hat (VEX)
8.7CVSS 4.0high——flatpak (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-290 · Authentication Bypass by Spoofing

  • Bypass Protection Mechanism
  • Gain Privileges or Assume Identity

Weakness & attack patterns

  • CWE-290

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-459 · Creating a Rogue Certification Authority CertificateCAPEC-21 · Exploitation of Trusted IdentifiersCAPEC-461 · Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-22 · Exploiting Trust in ClientCAPEC-473 · Signature SpoofCAPEC-476 · Signature Spoofing by MisrepresentationCAPEC-94 · Man in the Middle AttackCAPEC-59 · Session Credential Falsification through PredictionCAPEC-60 · Reusing Session IDs (aka Session Replay)
  • T1134Access Token Manipulation
  • T1528Steal Application Access Token
  • T1539Steal Web Session Cookie

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable xdg-dbus-proxy, Fedora, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10.
  • Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 8.8 (AV:N)

    Oct 2, 2026 · NVD

  3. Initial · CVE published

    Oct 2, 2026 · NVD

  4. CVE published by MITRE.

    Oct 2, 2026 · SOCRadar CTI

References

9 on the record

Coverage

1 story from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-94422 is xdg-dbus-proxy: message filtering bypass via reply serial allows sandbox escape, a high vulnerability affecting xdg-dbus-proxy, Fedora, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10 from flatpak, Fedora, Red Hat. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-94422. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.