# CVE-2026-5674: Pipewire: pipewire: sandbox escape and arbitrary code execution via malicious library loading > Attackers can escape sandboxes and execute arbitrary code by loading malicious libraries via PipeWire's PulseAudio compatibility layer. - **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Jul 2026 - **Updated:** 31 Aug 2026 - **Also known as:** ALSA-2026:47082, ALSA-2026:47083, AZL-110357, CLSA-2026-1790174444, DEBIAN-CVE-2026-5674, ECHO-41da-7bd5-f915, GHSA-c85p-55wv-w2q5, RHSA-2026:47082, RHSA-2026:47083, RHSA-2026:51064, RHSA-2026:56028, RHSA-2026:56029, RHSA-2026:61768, RLSA-2026:47082, RLSA-2026:47083, UBUNTU-CVE-2026-5674 ## What is CVE-2026-5674? CVE-2026-5674 is a high-severity code injection vulnerability in Red Hat Enterprise Linux 10, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A flaw was found in PipeWire, a multimedia server. This vulnerability allows an attacker to escape sandboxed applications, such as Flatpak, by exploiting PipeWire's PulseAudio compatibility layer. An attacker with minimal permissions within a sandboxed environment can load a malicious library, leading to arbitrary code execution outside the sandbox and potential compromise of the user's system. Weakness: CWE-427 (Uncontrolled Search Path Element) ## Which versions are affected by CVE-2026-5674? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pipewire` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-alsa` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-devel` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-gstreamer` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit-devel` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit-libs` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-libs` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-module-x11` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-plugin-libcamera` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-pulseaudio` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire-utils` | AlmaLinux:10 | All versions | 1.4.11-1.el10_2 | | `pipewire` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-alsa` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-devel` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-gstreamer` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-jack-audio-connection-kit` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-jack-audio-connection-kit-devel` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-jack-audio-connection-kit-libs` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-libs` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-module-x11` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-pulseaudio` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire-utils` | AlmaLinux:9 | All versions | 1.4.11-1.el9_8 | | `pipewire` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-alsa` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-alsa-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-gstreamer` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-gstreamer-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit-libs` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-jack-audio-connection-kit-libs-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-libs` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-libs-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-module-x11` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-module-x11-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | | `pipewire-plugin-libcamera` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.4.11-1.el10_2 | ## How do I fix CVE-2026-5674? Apply the vendor's patch. ## Is CVE-2026-5674 being exploited? There is no known exploitation of CVE-2026-5674 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-5674 and fix it if it is affected. What it is: CVE-2026-5674 is a high-severity code injection vulnerability in Red Hat Enterprise Linux 10, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-5674 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-5674/ (Markdown: https://insights.sbomify.com/CVE-2026-5674/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5674 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5674 - OSV: https://osv.dev/vulnerability/CVE-2026-5674 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-5674/ Summaries are generated and may contain mistakes; the official description above is the record.