RHSA-2026:8119HighCVSS 7.5

Red Hat Security Advisory: squid security update

Published
April 14, 2026
Last Modified
November 5, 2026

🔗 CVE IDs covered (2)

📋 Description

CVE-2026-32748 — Squid: Squid: Denial of Service via crafted ICP traffic CVE-2026-33526 — squid: Squid: Denial of Service via heap Use-After-Free vulnerability in ICP handling

🎯 Affected products14

  • Red Hat Enterprise Linux AppStream (v. 10)
  • squid-7:6.10-6.el10_1.3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-7:6.10-6.el10_1.3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-7:6.10-6.el10_1.3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-7:6.10-6.el10_1.3.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-7:6.10-6.el10_1.3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debuginfo-7:6.10-6.el10_1.3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debuginfo-7:6.10-6.el10_1.3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debuginfo-7:6.10-6.el10_1.3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debuginfo-7:6.10-6.el10_1.3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debugsource-7:6.10-6.el10_1.3.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debugsource-7:6.10-6.el10_1.3.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debugsource-7:6.10-6.el10_1.3.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • squid-debugsource-7:6.10-6.el10_1.3.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)

✅ 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 this issue, ensure that ICP support is not explicitly enabled in the Squid configuration. This can be achieved by commenting out or setting `icp_port` to `0` in the `squid.conf` file. After modifying the configuration, the Squid service must be reloaded or restarted for the changes to take effect. Example: ``` # icp_port 3130 ``` or ``` icp_port 0 ``` Warning: Reloading or restarting the Squid service may temporarily interrupt proxy services. Workaround: To mitigate this issue, disable ICP support in Squid by ensuring that `icp_port` is set to `0` in the `squid.conf` configuration file. This will prevent Squid from processing ICP traffic and eliminate the attack vector. After modifying the configuration, the Squid service must be restarted for the changes to take effect.

🔗 References (5)