CVE-2026-32748: squid-cache squid Improper Resource Locking

Vulnerability summary

CVE-2026-32748 is a high (CVSS 8.7) Improper Resource Locking vulnerability in squid-cache squid. EPSS estimates a 8.93% chance of exploitation in the next 30 days, higher than 95.2% of scored vulnerabilities.

Timeline

1. 26-03-2026
   PublishedVulnerability first disclosed.
2. 15-07-2026
   Last modifiedVulnerability information updated.

Description

Squid is a caching proxy for the Web. Prior to version 7.5, due to premature release of resource during expected lifetime and heap Use-After-Free bugs, Squid is vulnerable to Denial of Service when handling ICP traffic. This problem allows a remote attacker to perform a reliable and repeatable Denial of Service attack against the Squid service using ICP protocol. This attack is limited to Squid deployments that explicitly enable ICP support (i.e. configure non-zero `icp_port`). This problem _cannot_ be mitigated by denying ICP queries using `icp_access` rules. This bug is fixed in Squid version 7.5.

• CWE-413Improper Resource LockingThe product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.
• CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
• CWE-826Premature Release of Resource During Expected LifetimeThe product releases a resource that is still intended to be used by itself or another actor.