RHSA-2026:93447HighCVSS 8.6

Red Hat Security Advisory: libsoup security update

Published
November 2, 2026
Last Modified
November 2, 2026

🔗 CVE IDs covered (5)

CVE-2026-102560 →CVE-2026-102556 →CVE-2026-102557 →CVE-2026-102558 →CVE-2026-102559 →

📋 Description

CVE-2026-102556 — libsoup: libsoup: Heap buffer overflow from WebSocket Pong signal type confusion CVE-2026-102557 — libsoup: libsoup: Heap buffer overflow during WebSocket message reassembly CVE-2026-102558 — libsoup: libsoup: Heap buffer overflow during WebSocket receive-buffer growth CVE-2026-102559 — libsoup: libsoup: Heap buffer overflow during WebSocket client-frame masking CVE-2026-102560 — libsoup: libsoup: Heap buffer overflow during outgoing permessage-deflate buffer growth

🎯 Affected products22

  • Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-0:2.72.0-8.el9_2.18.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-0:2.72.0-8.el9_2.18.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-0:2.72.0-8.el9_2.18.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-0:2.72.0-8.el9_2.18.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-0:2.72.0-8.el9_2.18.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-0:2.72.0-8.el9_2.18.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debuginfo-0:2.72.0-8.el9_2.18.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debuginfo-0:2.72.0-8.el9_2.18.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debuginfo-0:2.72.0-8.el9_2.18.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debuginfo-0:2.72.0-8.el9_2.18.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debuginfo-0:2.72.0-8.el9_2.18.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debugsource-0:2.72.0-8.el9_2.18.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debugsource-0:2.72.0-8.el9_2.18.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debugsource-0:2.72.0-8.el9_2.18.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debugsource-0:2.72.0-8.el9_2.18.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-debugsource-0:2.72.0-8.el9_2.18.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-devel-0:2.72.0-8.el9_2.18.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-devel-0:2.72.0-8.el9_2.18.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-devel-0:2.72.0-8.el9_2.18.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-devel-0:2.72.0-8.el9_2.18.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • libsoup-devel-0:2.72.0-8.el9_2.18.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate avoid connecting custom handlers to SoupWebsocketConnection::pong, or avoid WebSocket use with untrusted peers. Workaround: To mitigate this set a conservative max-total-incoming-message-size / incoming payload limits where the API allows, and do not accept WebSocket connections from untrusted peers. Workaround: To mitigate this configure a finite max-incoming-payload-size (do not set it to 0/unlimited) on SoupWebsocketConnection. Restrict WebSocket exposure to trusted peers. Workaround: To mitigate this enforce application-level limits on outgoing WebSocket message sizes. Do not send untrusted bulk data as a single WebSocket message. Workaround: To mitigate this disable the permessage-deflate WebSocket extension if it is not required, and cap outgoing message sizes.

🔗 References (8)