Skip to main content
Public proof of conceptFix available

CVE-2025-62168

A public proof of concept exists; no exploitation attested.

  • Published2025-10-17
  • Fixed in7.2
  • WeaknessCWE-209 · CWE-550

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-10-1717:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-27 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-62168?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-62168?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Squid-cache squid
BranchAffectedFixed in
7.2< 7.27.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libecapAlmaLinux:8all versions · fixed in 1.0.1-2.module_el8.6.0+3048+383bc947and 1 other package
  • libecapAlmaLinux:8all versions · fixed in 1.0.1-2.module_el8.6.0+2741+01592ae8and 1 other package
  • squidAlmaLinux:10all versions · fixed in 7:6.10-6.el10_1.1
  • squidAlmaLinux:9all versions · fixed in 7:5.5-22.el9_7.1
  • squidAlmaLinux:8all versions · fixed in 7:4.15-10.module_el8.10.0+4055+645078d8.9

Vendor advisories

  • CVE-2025-62168 Red Hat Product Security225 products fixed · 4 known affected

    squid-cache: Squid vulnerable to information disclosure via authentication credential leakage in error handling

    squid as a component of Red Hat Enterprise Linux 6 · squid.src as a component of Red Hat Enterprise Linux 6 · squid34 as a component of Red Hat Enterprise Linux 6 · +1 more

  • RHSA-2025:21090 Red Hat Product Security18 products fixed

    Red Hat Security Advisory: squid:4 security update

  • RHSA-2025:21066 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: squid security update

  • RHSA-2025:21065 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: squid security update

  • RHSA-2025:21002 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: squid security update

  • RHSA-2025:20935 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: squid security update

8 more advisories

Full record on NVD

Fix

  1. Update Squid-cache squid to 7.2
  2. Vendor fix Red Hat Product Security RHSA-2025:21090 · 18 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2025:21090 · 18 productsThis vulnerability can be mitigated by disabling debug information in administration mailto links generated by Squid package. This can be accomplished in Red Hat Enterprise Linux by the following steps: 1) With administrative privileges, edit the squid configuration file located at ~~~/etc/squid/s…

Advisories and patches

Detection

read 2026-10-27 00:21 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
3 repositories, unverifiedmonzaviman/CVE-2025-62168shahroodcert/CVE-2025-62168nehkark/CVE-2025-62168
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2025-10-18
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.110read 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-209, CWE-550read 2026-10-23
  • FIRST EPSSEPSS score63.4 %read 2026-10-27
  • PoC-in-GitHubproof of concept3read 2026-10-27
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2025-10-17
Last Modified
2026-10-19
NVD status
Modified

Frequently asked questions

What is CVE-2025-62168?

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.

Is CVE-2025-62168 actively exploited?

Active exploitation of CVE-2025-62168 has not been confirmed. Its EPSS score was 63.4% on 2026-10-26, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-62168?

CVE-2025-62168 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running squid-cache? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month