CVE-2025-62168

HIGHNVD 7.510.0▲
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 15.7%, top 5% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 63%
CISA-KEV: Not listedEPSS: 63%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
10.0(medium)
EG Risk
—
EPSS
99.1%
KEV
Not listed

Published

October 17, 2025

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github.
generic Patch Available

oss-security - [CVE-2025-62168] SQUID-2025:2 Information Disclosure in Error handling

http://www.openwall.com/lists/oss-security/2025/11/05/6
github Patch Available

SQUID-2025:2 Information Disclosure in Error handling · Advisory · squid-cache/squid · GitHub

https://github.com/squid-cache/squid/security/advisories/GHSA-c8cc-phh7-xmxr
github_commit

commit 0951a0681011 (squid-cache/squid)

Fix landed in squid-cache/squid commit 0951a0681011 — awaiting tagged release

https://github.com/squid-cache/squid/commit/0951a0681011dfca3d78c84fd7f1e19c78a4443f

Vendor Advisories for CVE-2025-62168(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusquidclient (3.5.12-1ubuntu7.16+esm5) @ xenial2026-05-29ubuntu
redhatsquid-7:5.5-19.el9_6.22025-11-12redhat
redhatsquid-7:6.10-5.el10_0.12025-11-12redhat
redhatsquid:4-8040020251024000101.522a0ee42025-11-12redhat
redhatsquid-7:5.5-22.el9_7.12025-11-11redhat
redhatsquid-7:6.10-6.el10_1.12025-11-11redhat
redhatsquid:4-8020020251028004321.4cda2c842025-11-10redhat
redhatsquid:4-8080020251029094904.63b345852025-11-03redhat
redhatsquid:4-8060020251027230224.ad008a3a2025-10-30redhat
redhatsquid-7:5.2-1.el9_0.92025-10-28redhat
redhatsquid-7:3.5.20-17.el7_9.152025-10-28redhat
redhatsquid-7:5.5-5.el9_2.102025-10-28redhat
redhatsquid-7:5.5-13.el9_4.42025-10-28redhat
redhatsquid:4-8100020251023131551.489197e62025-10-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-16 17:02 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-13 22:29 UTCEPSS rescore
  9. 2026-07-13 06:12 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:09 UTCEPSS rescore
  13. 2026-07-06 11:41 UTCOSV refresh
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:55 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 09:56 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 37 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 23:43 UTCOSV refresh
  5. 2026-06-17 17:52 UTCEPSS rescore
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 17:48 UTCEPSS rescore
  8. 2026-06-15 17:48 UTCEPSS rescore
  9. 2026-06-14 23:18 UTCEPSS rescore
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:11 UTCEPSS rescore
  13. 2026-06-11 14:00 UTCEPSS rescore
  14. 2026-06-10 22:18 UTCEPSS rescore
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-06 13:47 UTCEPSS rescore
  20. 2026-06-06 13:47 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 06:10 UTCEPSS rescore
  24. 2026-06-05 06:10 UTCEPSS rescore
  25. 2026-06-04 13:12 UTCEPSS rescore
  26. 2026-06-04 13:12 UTCEPSS rescore
  27. 2026-06-02 20:13 UTCEPSS rescore
  28. 2026-06-02 20:12 UTCEPSS rescore
  29. 2026-06-01 13:51 UTCEPSS rescore
  30. 2026-06-01 13:51 UTCEPSS rescore
  31. 2026-05-31 22:30 UTCEPSS rescore
  32. 2026-05-31 22:30 UTCEPSS rescore
  33. 2026-05-31 00:16 UTCEPSS rescore
  34. 2026-05-31 00:16 UTCEPSS rescore
  35. 2026-05-29 20:35 UTCEG score recompute
  36. 2026-05-29 20:35 UTCVendor advisory
  37. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2025/CVE-2025-62168.yaml
    First seen Jan 1, 2025

    Squid Proxy - HTTP Authentication Credentials Disclosure

    Open source ↗

Frequently asked(5)

What is CVE-2025-62168?
CVE-2025-62168 is a high vulnerability published on October 17, 2025. 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…
When was CVE-2025-62168 disclosed?
CVE-2025-62168 was first published in the National Vulnerability Database on October 17, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-62168 actively exploited?
CVE-2025-62168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-62168?
CVE-2025-62168 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 10.0.
How do I remediate CVE-2025-62168?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-62168, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-62168

Explore →

Is Your Infrastructure Affected by CVE-2025-62168?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs