Skip to main content
Mallory
UnratedVulnerability

CVE-2026-104786: Stack-based buffer overflow in Squid peer Basic authentication

Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-104786CWE-121

CVE-2026-104786 is a stack-based buffer overflow in the HTTP authentication handling of Squid 5.x, 6.x, and 7.x releases before 7.7. Improper input validation allows a trusted client to trigger an out-of-bounds write when Squid authenticates to a configured cache_peer using client-supplied Basic authentication credentials. Exploitation can corrupt memory and affect service integrity and availability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt stack memory, potentially disrupting the Squid service and affecting its integrity. The vulnerability-specific assessment identifies low integrity and availability impacts and no confidentiality impact. Broader distribution-level severity assessments conflict with this assessment; arbitrary code execution and information disclosure are not established by the available technical details.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed package can be deployed, avoid configuring Squid to authenticate to a cache_peer using client-provided Basic authentication credentials. Restrict proxy access to necessary clients as a defense-in-depth measure, noting that a trusted client can trigger the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade to Squid 7.7 or later, or apply the patch referenced in vendor advisory SQUID-2026:7. Distribution packages may contain backported fixes without adopting the upstream version number. For Debian stable (trixie), upgrade squid to version 6.13-2+deb13u4 or later. For Amazon Linux 2023, install the updated Squid packages associated with ALAS2023-2026-3454. These distribution updates do not establish fix availability for Debian 12; verify that release separately.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-104786 exploited in the wild?
As of Nov 13, 2026, Mallory has no reports of CVE-2026-104786 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-104786?
As of Nov 13, 2026, Mallory has found no public exploit for CVE-2026-104786.
Is there a patch for CVE-2026-104786?
Upgrade to Squid 7.7 or later, or apply the patch referenced in vendor advisory SQUID-2026:7. Distribution packages may contain backported fixes without adopting the upstream version number.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 12, 2026Amazon Linux 2023 : squid (ALAS2023-2026-3454) | Tenable®A vulnerability affecting Squid packages distributed with Amazon Linux 2023. The listed CVSS v3 vector indicates network-based exploitation requiring no privileges or user interaction, with high confidentiality, integrity, and availability impacts. The content does not describe the underlying flaw. The vulnerability publication date is November 5, 2026, and patches were published November 12, 2026.Read more ↗tenable nessus pluginsNews · Nov 6, 2026Squid 5.x < 7.7 Stack-based Buffer Overflow (SQUID-2026:7) | Tenable®An improper input validation flaw causes a stack-based buffer overflow in Squid's HTTP authentication handling. It affects Squid 5.x, 6.x, and 7.x before 7.7 when client-supplied Basic authentication credentials are forwarded to a cache_peer. A trusted client can trigger an out-of-bounds write, affecting integrity and availability. The reported CVSS v3 score is 5.4 (Medium). Nessus identifies exposure using the application's self-reported version rather than testing exploitation. Upgrade to Squid 7.7 or later, or apply the vendor advisory's patch.Read more ↗aws alasNews · Nov 6, 2026CVE-2026-104786An improper input validation vulnerability in Squid's HTTP authentication permits a stack-based buffer overflow. The advisory rates it Important, with a CVSS v3.1 score of 7.1. Its vector indicates network exploitation with low privileges, low attack complexity, and no user interaction, with high availability impact, low integrity impact, and no confidentiality impact. Amazon Linux 2 Core is not affected; no fix is planned for the Amazon Linux 2 Squid4 Extra package, while fixes are pending for Amazon Linux 2023 and Amazon Linux 2027 Preview.Read more ↗tenable nessus pluginsNews · Nov 3, 2026Linux Distros Unpatched Vulnerability : CVE-2026-104786 | Tenable®A critical vulnerability affecting the Squid package on Debian Linux 12, reported by Nessus plugin 375600. The CVSS v3 score is 9.8, indicating network-based exploitation without authentication or user interaction and potentially high confidentiality, integrity, and availability impacts. The content does not describe the underlying flaw. The vendor indicates it will not be patched, and no known solution or exploits are available. Detection relies on vendor-reported package presence rather than exploitation testing.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.