Squid
Squid vulnerable to information disclosure via authentication credential leakage in error handling
Squid is a caching proxy for the Web. In Squid versions prior to 7.2, a failure to redact HTTP authentication credentials in error handling allows information disclosure. The vulnerability allows a script to bypass browser security protections and learn the credentials a trusted client uses to authenticate. This potentially allows a remote client to identify security tokens or credentials used internally by a web application using Squid for backend load balancing. These attacks do not require Squid to be configured with HTTP authentication. The vulnerability is fixed in version 7.2. As a workaround, disable debug information in administrator mailto links generated by Squid by configuring squid.conf with email_err_data off.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 7.2
Fixed in 7.2
Mitigation
Upgrade squid to 7.2 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 4.8 days after publication; not in CISA KEV. First PoC: monzaviman/CVE-2025-62168 (created 22 Oct 2025, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| monzaviman/CVE-2025-62168 | 22 Oct 2025 +4.8 d | 16 | PoC |
| shahroodcert/CVE-2025-62168 | 2 Nov 2025 +16 d | 1 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| nehkark/CVE-2025-62168 | 25 Nov 2025 +39 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Squid Proxy - HTTP Authentication Credentials Disclosure | 1 Apr 2026 | 14 Nov 2026 |