Service interruption via stale ICP request reuse
Published Mar 26, 2026 · Updated Mar 26, 2026
Use-after-free in Squid before 7.5 allows remote attackers to interrupt the proxy service by sending ICPv3 queries to an enabled ICP port. In ICPv3 request handling, ACLFilledChecklist releases an unlocked HttpRequest, and Squid dereferences the destroyed object after icpAccessAllowed returns. The attack requires a nonzero icp_port, needs no authentication, and repeatedly interrupts the proxy even when icp_access rules deny queries.
Summary
What happened
Use-after-free in Squid before 7.5 allows remote attackers to interrupt the proxy service by sending ICPv3 queries to an enabled ICP port. In ICPv3 request handling, ACLFilledChecklist releases an unlocked HttpRequest, and Squid dereferences the destroyed object after icpAccessAllowed returns. The attack requires a nonzero icp_port, needs no authentication, and repeatedly interrupts the proxy even when icp_access rules deny queries.
The record
- CVE
- CVE-2026-32748
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- Squid Software Foundation
- Product
- Squid
- Classifications
- CWE-826, CWE-413, CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo