Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-62168: HTTP Authentication Credential Disclosure in Squid Error Handling

Published Oct 17, 2025 · Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS7.5High · v3.1
EPSS61.6%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Squid-Cache
IdentifiersCVE-2025-62168CWE-209 · Generation of Error Message…

CVE-2025-62168 is an information disclosure vulnerability in Squid versions prior to 7.2. Squid fails to redact HTTP authentication credentials when generating error responses containing administrator mailto links with request debugging information. Sensitive headers, including Authorization, can consequently appear in the generated error page. An attacker-controlled script can bypass browser security protections to learn credentials used by a trusted client. In backend load-balancing deployments, remote clients may also obtain internal application credentials or security tokens. Both forward and reverse proxy deployments can be affected, even when Squid itself is not configured for HTTP authentication.

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 exposes authentication material, potentially including usernames, passwords, and bearer tokens. Disclosure can compromise client authentication secrets or credentials used internally between applications and backend services. Depending on the exposed credentials' privileges and validity, attackers may impersonate their owners and access protected resources.

Mitigation

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

Set email_err_data off in the Squid configuration to disable request debugging information in administrator mailto links generated on error pages.

Remediation

Patch, then assume compromise.

Upgrade to Squid 7.2 or a later release containing the fix, or install the applicable vendor-provided Squid security update that backports it. The fix redacts sensitive authentication headers before including request details in generated error content.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Squid-CacheSquidapplication
FAQ

Frequently asked questions

Is CVE-2025-62168 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2025-62168 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-62168?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-62168, the earliest disclosed Nov 25, 2025.
Is there a patch for CVE-2025-62168?
Upgrade to Squid 7.2 or a later release containing the fix, or install the applicable vendor-provided Squid security update that backports it. The fix redacts sensitive authentication headers before including request details in generated error content.
What products are affected by CVE-2025-62168?
Squid-Cache Squid.
How severe is CVE-2025-62168?
CVE-2025-62168 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 61.6% (99th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

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

View more in app →
+5 more in the timeline. Sign up to see them
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 activity7Community discussion across Reddit, Mastodon, and other social sources.