CVE-2026-133004: Medium severity debian/pipewire vulnerability

Published Nov 19, 2026
·
Updated

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 AFINET peer, or a socket configured with the client.access option) can set pipewire.client.access=allowed in its own SETCLIENTNAME 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 (PWPERMALL) 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 (AFUNIX 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).

Affected Software

4 affected components
debian/pipewire*
debian/pipewire*
debian/pipewire*
debian/pipewire<=0.3.65-3+deb12u1, <=1.4.2-1, <=1.6.9-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 8e3a214ecfd9aece7eaabb67d29ade3496b9bbdf

Event History

Nov 19, 2026
Data Sourced
via Red Hat·10:23 AM
DescriptionSeverityAffected Software
Nov 20, 2026
CVE Published
via OSV·03:47 PM
Data Sourced
via OSV·03:47 PM
DescriptionAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203