OESA-2026-4580: squid security update

Published Oct 29, 2026
·
Updated

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. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (src/HttpHeader.cc) accepted the bare Transfer-Encoding: identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients' future requests. This issue is fixed in version 7.6.(CVE-2026-61642)

Affected Software

1 affected componentFixes available
openeuler/squid<6.6-10.oe2403sp4
6.6-10.oe2403sp4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/squid to a version that resolves this vulnerability.

    Fixed in 6.6-10.oe2403sp4
  2. Upgrade

    Upgrade Squid to a version that resolves this vulnerability.

    Fixed in 7.6

Event History

Oct 29, 2026
Advisory Published
via OSV·09:03 AM
Data Sourced
via OSV·09:03 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Who can exploit this issue?

An attacker must be a trusted client able to send HTTP/1.1 requests to the affected Squid instance. The flaw can let that client bypass security mechanisms deployed between the attacker and Squid.

2

When is the impact more severe?

Risk increases when an HTTP cache operates in front of the affected Squid instance. In that arrangement, an attacker may poison the upstream cache with arbitrary malicious content at any URL, affecting future client requests.

3

What version contains the fix?

The issue affects Squid versions from 3.3.0.1 through versions before 7.6. It is fixed in Squid 7.6.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203