Bug 2576325 (CVE-2026-133004)

Summary: CVE-2026-133004 pipewire: pipewire: pipewire-pulse client can overwrite the server-computed access label to bypass audio access restrictions
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in PipeWire's PulseAudio compatibility server. A local application connecting to the PipeWire PulseAudio socket could override the access restrictions assigned to it by the server and gain unrestricted access to the audio devices and streams of the user's session, instead of the limited access intended for restricted or sandboxed applications. As a result, a malicious application running in a sandbox, such as a Flatpak application granted access to the PulseAudio socket, could observe or modify audio streams belonging to other applications of the same user.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2576333, 2576335, 2576331, 2576332, 2576334    
Bug Blocks:    

Description OSIDB Bzimport 2026-11-19 10:23:22 UTC
Summary: In PipeWire's module-protocol-pulse, the connecting client's own PulseAudio proplist is parsed into the same property set that holds the server-computed pipewire.client.access label, with no key filtering. A client that the server deliberately labelled (a Flatpak peer, an AF_INET peer, or a socket configured with the client.access option) can set pipewire.client.access=allowed in its own SET_CLIENT_NAME proplist and overwrite that label. pipewire-pulse forwards the overwritten label to the PipeWire daemon when connecting on the client's behalf, and module-access in its default legacy mode grants unrestricted access (PW_PERM_ALL) instead of leaving the client for the session manager to restrict.

Impact: full read/write/execute/metadata access to the audio graph of the user's session - see and modify all nodes and streams, read other applications' client records, capture microphone and other applications' audio. No code execution, no cross-user access, not remotely exploitable (AF_UNIX socket). Ordinary non-sandboxed local applications are already unrestricted in the default configuration and are unaffected.

Prerequisites: local code execution as the user; the client must be one the pulse server deliberately labels (realistic case: a Flatpak application with --socket=pulseaudio; also operator-configured client.access sockets and the non-default TCP listener). The PulseAudio authentication cookie is not verified (see CVE-2026-5674).

Affected versions: introduced in 0.3.43 (commit 22625fb65, 2022-01-04, pulse-server: support server config); verified present in pipewire 1.2.7 (RHEL 10.0), 1.4.11 (RHEL 9.8) and 1.6.9 (CentOS Stream 10). module-protocol-pulse is not built for RHEL 8 (pulse support disabled in the spec for RHEL < 9).

Fixed upstream: master commit 8e3a214ecfd9aece7eaabb67d29ade3496b9bbdf (pulse-server: avoid updating pipewire. properties, 2026-11-16); a 1.6 backport is planned. No released tarball contains the fix at the time of writing.

Reported by Calif.io via PSIRTSUPT-30611 (reporter reference ANT-2026-GW6KQAZJ). Red Hat independently reproduced the issue on RHEL 10-lineage packages (pipewire 1.4.11) with an own reproducer: a labelled pulse socket client that sends pipewire.client.access=allowed in its proplist is granted unrestricted access, while the same client without the property remains restricted.

CVSS: RH CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L = 5.3 (Moderate).