CVE-2026-33515

Squid is a high-performance proxy caching server. It handles all requests in a single, non-blocking, I/O-driven process and keeps meta data and implements negative caching of failed requests.

Security Fix(es):

Squid is a widely used proxy caching server. Due to premature release of resources and heap Use-After-Free bugs during the handling of ICP (Internet Cache Protocol) traffic, Squid is vulnerable to Denial of Service. A remote attacker can cause the Squid service to crash by sending specially crafted ICP requests to a Squid instance with ICP support enabled, resulting in a reliable and repeatable Denial of Service attack. This vulnerability only affects Squid deployments that explicitly enable ICP support (i.e., configure a non-zero icp_port). It is important to note that this problem cannot be mitigated by denying ICP queries using icp_access rules.(CVE-2026-32748)

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.(CVE-2026-33515)

Squid is a caching proxy for the Web. Prior to version 7.5, due to heap Use-After-Free, 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. Version 7.5 contains a patch.(CVE-2026-33526)

Squid is a high-performance proxy caching server. It handles all requests in a single, non-blocking, I/O-driven process and keeps meta data and implements negative caching of failed requests.

Security Fix(es):

Squid is a widely used proxy caching server. Due to premature release of resources and heap Use-After-Free bugs during the handling of ICP (Internet Cache Protocol) traffic, Squid is vulnerable to Denial of Service. A remote attacker can cause the Squid service to crash by sending specially crafted ICP requests to a Squid instance with ICP support enabled, resulting in a reliable and repeatable Denial of Service attack. This vulnerability only affects Squid deployments that explicitly enable ICP support (i.e., configure a non-zero icp_port). It is important to note that this problem cannot be mitigated by denying ICP queries using icp_access rules.(CVE-2026-32748)

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.(CVE-2026-33515)

Squid is a caching proxy for the Web. Prior to version 7.5, due to heap Use-After-Free, 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. Version 7.5 contains a patch.(CVE-2026-33526)

Squid is a high-performance proxy caching server. It handles all requests in a single, non-blocking, I/O-driven process and keeps meta data and implements negative caching of failed requests.

Security Fix(es):

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.(CVE-2026-33515)

Squid is a caching proxy for the Web. Prior to version 7.5, due to heap Use-After-Free, 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. Version 7.5 contains a patch.(CVE-2026-33526)

Squid is a high-performance proxy caching server. It handles all requests in a single, non-blocking, I/O-driven process and keeps meta data and implements negative caching of failed requests.

Security Fix(es):

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.(CVE-2026-33515)

Squid is a caching proxy for the Web. Prior to version 7.5, due to heap Use-After-Free, 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. Version 7.5 contains a patch.(CVE-2026-33526)

Squid is a high-performance proxy caching server. It handles all requests in a single, non-blocking, I/O-driven process and keeps meta data and implements negative caching of failed requests.

Security Fix(es):

Squid is a widely used proxy caching server. Due to premature release of resources and heap Use-After-Free bugs during the handling of ICP (Internet Cache Protocol) traffic, Squid is vulnerable to Denial of Service. A remote attacker can cause the Squid service to crash by sending specially crafted ICP requests to a Squid instance with ICP support enabled, resulting in a reliable and repeatable Denial of Service attack. This vulnerability only affects Squid deployments that explicitly enable ICP support (i.e., configure a non-zero icp_port). It is important to note that this problem cannot be mitigated by denying ICP queries using icp_access rules.(CVE-2026-32748)

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.(CVE-2026-33515)

Squid is a caching proxy for the Web. Prior to version 7.5, due to heap Use-After-Free, 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. Version 7.5 contains a patch.(CVE-2026-33526)

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.

Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. 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. Version 7.5 contains a patch.

• CVE-2025-59362: fix ASN.1 encoding of long SNMP OIDs
• CVE-2026-33526: do not escape malformed URI twice when sending ICP errors
• CVE-2026-33515: fix validation of ICP packet sizes and URLs

• CVE-2026-33526: fix heap use-after-free due to double rfc1738_escape in ICP error handling
• CVE-2026-33515: fix validation of ICP packet sizes and URLs to prevent out-of-bounds reads
• CVE-2026-32748: fix HttpRequest use-after-free in ICP v3 query handling

• CVE-2026-33526: fix heap use-after-free due to double rfc1738_escape in ICP error handling
• CVE-2026-33515: fix validation of ICP packet sizes and URLs to prevent out-of-bounds reads
• CVE-2026-32748: fix HttpRequest use-after-free in ICP v3 query handling

• CVE-2026-33526: fix heap use-after-free due to double rfc1738_escape in ICP error handling
• CVE-2026-33515: fix validation of ICP packet sizes and URLs to prevent out-of-bounds reads
• CVE-2026-32748: fix HttpRequest use-after-free in ICP v3 query handling

• CVE-2026-33526: fix heap Use-After-Free in ICP traffic handling causing DoS
• CVE-2026-33515: fix out-of-bounds read in ICP message handling leaking sensitive information
• CVE-2026-32748: fix HttpRequest lifetime in ICP v3 queries preventing Use-After-Free DoS

• SECURITY UPDATE: Denial of Service in ICP request handling via double rfc1738_escape() call causing heap use-after-free
  • debian/patches/CVE-2026-33526.patch: Remove redundant rfc1738_escape() call in icpGetRequest()
  • CVE-2026-33526
• SECURITY UPDATE: Denial of Service in ICP v3 query handling via use-after-free of HttpRequest object
  • debian/patches/CVE-2026-32748.patch: Add proper HTTPMSGLOCK/HTTPMSGUNLOCK to doV3Query() to match doV2Query() locking pattern
  • CVE-2026-32748
• SECURITY UPDATE: Out-of-bounds read in ICP message handling allows information disclosure
  • debian/patches/CVE-2026-33515.patch: Add icpGetUrl() validation function to check packet bounds and NUL-termination of URLs in ICP messages
  • CVE-2026-33515

• CVE-2026-33526: fix heap Use-After-Free in ICP traffic handling causing DoS
• CVE-2026-33515: fix out-of-bounds read in ICP message handling leaking sensitive information
• CVE-2026-32748: fix HttpRequest lifetime in ICP v3 queries preventing Use-After-Free DoS

• CVE-2026-33515: fix validation of packet sizes and URLs in ICP
• CVE-2026-33526: fix escaping malformed URI twice when sending ICP errors

• CVE-2026-32748: ICP: fix HttpRequest lifetime for ICP v3 queries
• CVE-2026-33515: ICP: fix validation of packet sizes and URLs
• CVE-2026-33526: do not escape malformed URI twice when sending ICP errors

• CVE-2026-32748: ICP: fix HttpRequest lifetime for ICP v3 queries
• CVE-2026-33515: ICP: fix validation of packet sizes and URLs
• CVE-2026-33526: do not escape malformed URI twice when sending ICP errors

• CVE-2026-32748: ICP: fix HttpRequest lifetime for ICP v3 queries
• CVE-2026-33515: ICP: fix validation of packet sizes and URLs
• CVE-2026-33526: do not escape malformed URI twice when sending ICP errors

• SECURITY UPDATE: out-of-bounds read when handling malformed ICP traffic
  • debian/patches/CVE-2026-33515.patch: validate ICP packet sizes and URLs in icpGetUrl(); reject non-NUL-terminated URLs, URLs with embedded NULs or trailing garbage; guard icpHandleUdp() against a nil icpOutgoingConn pointer
  • CVE-2026-33515

Squid mishandles ASN.1 encoding of long SNMP OIDs. This occurs in asn_build_objid in lib/snmplib/asn1.c. (CVE-2025-59362) Squid vulnerable to information disclosure via authentication credential leakage in error handling. (CVE-2025-62168) Squid vulnerable to Denial of Service in ICP Request handling. (CVE-2026-33526) Squid has Denial of Service in ICP Response handling. (CVE-2026-32748) Squid has issues in ICP message handling. (CVE-2026-33515)

These are all security issues fixed in the squid-7.7-2.1 package on the GA media of openSUSE Tumbleweed.

This update for squid fixes the following issues:

• CVE-2026-32748: denial of service in ICP Request handling (bsc#1260453).
• CVE-2026-33515: out of bounds read in ICP message handling (bsc#1260454).
• CVE-2026-33526: denial of service in ICP Request handling (bsc#1260452).
• CVE-2026-47729: out-of-bounds read attack against the ftp gateway due to a improper validation of syntactic correctness of input (bsc#1268272).
• CVE-2026-50012: Improper Input Validation bug (bsc#1268320).

Changes for squid:

Update to 6.14:

• Do not leak HttpReply when checking http_reply_access (bsc#1237027)

This update for squid fixes the following issues:

• CVE-2026-32748: denial of service in ICP Request handling (bsc#1260453).
• CVE-2026-33515: out of bounds read in ICP message handling (bsc#1260454).
• CVE-2026-33526: denial of service in ICP Request handling (bsc#1260452).
• CVE-2026-47729: out-of-bounds read attack against the ftp gateway due to a improper validation of syntactic correctness of input (bsc#1268272).
• CVE-2026-50012: Improper Input Validation bug (bsc#1268320).

Changes for squid:

Update to 6.14:

• Do not leak HttpReply when checking http_reply_access (bsc#1237027)

This update for squid fixes the following issues:

• CVE-2026-32748: denial of service in ICP Request handling (bsc#1260453).
• CVE-2026-33515: out of bounds read in ICP message handling (bsc#1260454).
• CVE-2026-33526: denial of service in ICP Request handling (bsc#1260452).
• CVE-2026-47729: out-of-bounds read attack against the ftp gateway due to a improper validation of syntactic correctness of input (bsc#1268272).
• CVE-2026-50012: Improper Input Validation bug (bsc#1268320).

Changes for squid:

• Do not leak HttpReply when checking http_reply_access (bsc#1237027)
• Updated to version 6.14

This update for squid fixes the following issues:

• CVE-2023-5824: Multiple issues in HTTP response caching (bsc#1216496).
• CVE-2023-49288: Use-After-Free in the HTTP Collapsed Forwarding Feature (bsc#1217825).
• CVE-2025-62168: failure to redact HTTP authentication credentials in error handling leads to the disclosure of credentials a trusted client uses to authenticate (bsc#1252281).
• CVE-2026-32748: denial of service in ICP Request handling (bsc#1260453).
• CVE-2026-33515: out of bounds read in ICP message handling (bsc#1260454).
• CVE-2026-33526: denial of service in ICP Request handling (bsc#1260452).
• CVE-2026-47729: out-of-bounds read attack against the ftp gateway due to a improper validation of syntactic correctness of input (bsc#1268272).
• CVE-2026-50012: Improper Input Validation bug (bsc#1268320).

It was discovered that Squid incorrectly handled certain HTTP Transfer- Encoding headers. An attacker could possibly use this issue to perform HTTP request smuggling attacks, bypass security mechanisms, or poison web caches. (CVE-2026-61642)

It was discovered that Squid incorrectly handled certain cache digest replies, which could lead to a buffer overflow. A remote attacker could possibly use this issue to cause Squid to crash, resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2026-50012)

It was discovered that Squid incorrectly handled parsing certain FTP directory listings. A remote attacker could possibly use this issue to obtain sensitive information. This issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2026-47729)

It was discovered that Squid incorrectly handled certain ICP traffic. A remote attacker could possibly use this issue to cause Squid to crash, resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2026-32748, CVE-2026-33526)

It was discovered that Squid incorrectly handled certain ICP requests. A remote attacker could possibly use this issue to obtain sensitive information. This issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2026-33515)