SecOps SignalSecurity Intelligence Workspace
Collection Degraded29 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2026-61642Public Intelligence Dossier
Source: Microsoft · Limited verification•Last verified: •Collection Degraded
CVE-2026-61642Unknown / EvaluatingImportant (raw)CVSS 7.7CWE-444

Squid Request Smuggling in HTTP Transfer-Encoding

Published: 17 Oct 2026•Last updated: 17 Oct 2026, 06:38 AM IST•Source identifier: security-advisories@github.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance not available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
7.7Important (raw)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Metric sourceMicrosoft MSRC CVRF
EPSS probability
4.7%0.047
Percentile92nd
Weakness type
CWE-444
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

High

Actively exploited

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; No confirmed exploitation signal in current enrichment

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • azl3 squid 6.13-5 on Azure Linux 3.0 · version range not provided by source · Microsoft MSRC · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • Microsoft MSRC: Release Notes

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

No rule-based guidance for this vulnerability class

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
security-advisories@github.com
Record status · verification
UPDATED · NVD API
CPE
Unknown

Evidence & Provenance

3 public sources
api.msrc.microsoft.comSource recordnvd.nist.govSource recordgithub.comSource record
Detection Hunting Query

— No published hunting query names this record. Browse community and library queries instead.

Open KQL Library

Correlated briefings

Microsoft Security Update Guide · Limited verificationOctober 2026 Security UpdatesPublished 13 Oct 2026
SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.