Skip to main content
CVE-2025-62168VulnerabilityPublished

SUSE · Security update for squid

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2025-62168· Critical 10.0

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical : upgrade SUSE squid to 7.2 as a priority.

Data as of 29 Oct 2026, 23:31 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 7.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 2025

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade squid-cache/squid to 7.2.

Affected software

ProductAffectedFixed in
GitHubsquid-cache/squidpkg:github/squid-cache/squidOther threatsAffected
  • <7.2
Fixed in
  • 7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the security update provided by the SUSE Product Security Team to fix the vulnerability. Since the vendor advisory indicates the issue is fixed, ensure systems are updated to the patched version. No additional mitigation actions are specified.

Description

A security update for the Squid proxy server addresses a vulnerability identified as CVE-2025-62168, which allowed proxy authentication data to be visible to scripts. This issue has been fixed by the SUSE Product Security Team.

References

Community reviews

Loading reviews…