Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NSummary
CVE-2025-62168 is a critical-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Squid-Cache Squid. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-11 (Error Handling) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-62168 is an information disclosure vulnerability in Squid, an open-source caching proxy for the web, affecting versions prior to 7.2. The issue stems from a failure to redact HTTP authentication credentials during error handling, which exposes these credentials in generated error messages. This flaw, associated with CWE-209 (Generation of Error Message Containing Sensitive Information) and CWE-550 (Information Exposure Through Directory Listing), carries a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N), indicating critical severity due to its network accessibility, low complexity, lack of privileges or user interaction required, and high impacts on confidentiality and integrity with scope expansion.
Remote attackers can exploit this vulnerability without needing Squid to be configured for HTTP authentication. By triggering an error condition, an attacker-controlled script can bypass browser security protections, such as same-origin policy, to extract authentication credentials used by a trusted client. This enables a remote client to learn security tokens or internal credentials employed by web applications that use Squid for backend load balancing, potentially compromising application authentication mechanisms.
The vulnerability is fixed in Squid version 7.2, as detailed in the official GitHub commit (0951a0681011dfca3d78c84fd7f1e19c78a4443f) and security advisory (GHSA-c8cc-phh7-xmxr). A workaround involves disabling debug information in administrator mailto links by adding "email_err_data off" to squid.conf, as noted in the OSS-security mailing list announcement. Security practitioners should upgrade to version 7.2 or apply the workaround and monitor for anomalous error responses.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-34894
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V16.5.1V14.2.1
Mitigating Controls (NIST 800-53 r5) AI
si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards explicitly forbid exposing sensitive data in errors.
Security testing can detect error messages that leak sensitive information.
Logging policy can require suppression of sensitive data in error messages.
Secure SDLC mandates error-handling rules that avoid leaking sensitive information.
Application security requirements can specify safe error messaging.
Secure architecture principles include proper exception handling.