This page was not yet optimized for use on mobile devices.
CVE-2025-62168
Data ?
| Vulnerability ID | CVE-2025-62168 |
|---|---|
| Published on | 17.10.2025 17:15 |
| Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:squid-cache:squid:2.0:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.1:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.2:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.3:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.4:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable1:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable2:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable3:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable4:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.