Is CVE-2026-14324 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-14324 being exploited in the wild.

How severe is CVE-2026-14324?

Medium severity, with a CVSS score of 6.5, published 1 July 2026.

Which products and versions are affected?

Red Hat Enterprise Linux 8 pipewire, pipewire0.2; Red Hat Enterprise Linux 9 pipewire; Red Hat Enterprise Linux 10 pipewire, libkrun.

Is there a fix for CVE-2026-14324?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-14324 attacked?

It is attacked from the adjacent network, in an operating system.

Am I affected by CVE-2026-14324?

Check whether you run Red Hat Libkrun or Red Hat PipeWire. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-14324: Red Hat PipeWire NULL pointer dereference in RAOP module

CVE-2026-14324 · Severity: medium · CVSS 6.5 · Published 2026-07-01

A vulnerability exists in PipeWire, a core Linux service responsible for handling audio and video streams. An attacker using a malicious AirPlay-compatible device on the same local network can send specially crafted data to crash the PipeWire service. This results in a loss of audio and video functionality for the affected user, potentially disrupting communications or media playback.

Technologies: Red Hat PipeWire. Vendors: Red Hat.

Quick answers

Is CVE-2026-14324 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-14324 being exploited in the wild.
How severe is CVE-2026-14324?: Medium severity, with a CVSS score of 6.5, published 1 July 2026.
Which products and versions are affected?: Red Hat Enterprise Linux 8 pipewire, pipewire0.2; Red Hat Enterprise Linux 9 pipewire; Red Hat Enterprise Linux 10 pipewire, libkrun.
Is there a fix for CVE-2026-14324?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-14324 attacked?: It is attacked from the adjacent network, in an operating system.
Am I affected by CVE-2026-14324?: Check whether you run Red Hat Libkrun or Red Hat PipeWire. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A flaw was identified in the PipeWire RAOP (Remote Audio Output Protocol) RTSP client module. The component fails to validate 'Content-Length' headers in RTSP responses from remote servers and neglects to check the return value of the 'pw_array_add()' function. An attacker on the local network (adjacent) can simulate a rogue AirPlay device and send a response with an excessively large Content-Length. This leads to a failed memory allocation and a subsequent NULL pointer dereference (CWE-476), resulting in a denial-of-service (DoS) condition by crashing the PipeWire daemon.

Affected products

Red Hat Enterprise Linux 8 pipewire, pipewire0.2
Red Hat Enterprise Linux 9 pipewire
Red Hat Enterprise Linux 10 pipewire, libkrun

Timeline

2026-07-01: disclosed: Initial report via Red Hat Bugzilla and NVD publication.
2026-07-01: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.