Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-62168: Squid vulnerable to information disclosure via authentication credential leakage in error handling

HighCVSS 7.5 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 48/100)

  • A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 61.5% (FIRST EPSS); higher than 99.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: squid-cache squid 7.2; azl3 squid 6.13-1 on Azure Linux 3.0 6.13-3; azl3 squid 6.13-3 on Azure Linux 3.0 6.13-3.
  • Severity is disputed: the assigning authority (CNA) scores it 10.0, NVD 7.5.

Add it to your regular patch cycle. Upgrade to squid-cache squid 7.2; azl3 squid 6.13-1 on Azure Linux 3.0 6.13-3; azl3 squid 6.13-3 on Azure Linux 3.0 6.13-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 17, 2025
Updated
Oct 19, 2026
EPSS
61.5% · 99th percentile

Report tools

JSON

Action score

48

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
18 / 30 · 61.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
10.0
2.5 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-62168

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for squid-cache records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
squid-cachesquid

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • squid-cache squid

    • < 7.2affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • squid-cache squidbefore 7.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10squidbefore 7:6.10-6.el10_1.17:6.10-6.el10_1.1
AlmaLinux:8libecapbefore 1.0.1-2.module_el8.6.0+2741+01592ae81.0.1-2.module_el8.6.0+2741+01592ae8
AlmaLinux:8libecapbefore 1.0.1-2.module_el8.6.0+3048+383bc9471.0.1-2.module_el8.6.0+3048+383bc947
AlmaLinux:8libecap-develbefore 1.0.1-2.module_el8.6.0+3048+383bc9471.0.1-2.module_el8.6.0+3048+383bc947
AlmaLinux:8libecap-develbefore 1.0.1-2.module_el8.6.0+2741+01592ae81.0.1-2.module_el8.6.0+2741+01592ae8
AlmaLinux:8squidbefore 7:4.15-10.module_el8.10.0+4055+645078d8.97:4.15-10.module_el8.10.0+4055+645078d8.9
AlmaLinux:9squidbefore 7:5.5-22.el9_7.17:5.5-22.el9_7.1
Alpine:v3.23squidbefore 7.3-r07.3-r0
Debian:11squidbefore 4.13-10+deb11u64.13-10+deb11u6
Debian:12squidbefore 5.7-2+deb12u45.7-2+deb12u4
Debian:13squidbefore 6.13-2+deb13u16.13-2+deb13u1
Debian:14squidbefore 7.2-17.2-1
openSUSE:Leap 15.6squidbefore 6.10-150600.3.14.16.10-150600.3.14.1
openSUSE:Leap 16.0squidbefore 6.12-160000.3.16.12-160000.3.1
openSUSE:Tumbleweedsquidbefore 7.3-1.17.3-1.1
Red Hat:enterprise_linux_eus:10.0squidbefore 7:6.10-5.el10_0.17:6.10-5.el10_0.1
Red Hat:enterprise_linux_eus:10.0squid-debuginfobefore 7:6.10-5.el10_0.17:6.10-5.el10_0.1
Red Hat:enterprise_linux_eus:10.0squid-debugsourcebefore 7:6.10-5.el10_0.17:6.10-5.el10_0.1
Red Hat:enterprise_linux:10.1squidbefore 7:6.10-6.el10_1.17:6.10-6.el10_1.1
Red Hat:enterprise_linux:10.1squid-debuginfobefore 7:6.10-6.el10_1.17:6.10-6.el10_1.1
Red Hat:enterprise_linux:10.1squid-debugsourcebefore 7:6.10-6.el10_1.17:6.10-6.el10_1.1
Red Hat:enterprise_linux:8::appstreamlibecapbefore 0:1.0.1-2.module+el8.9.0+19703+a1da72230:1.0.1-2.module+el8.9.0+19703+a1da7223
Red Hat:enterprise_linux:8::appstreamlibecap-debuginfobefore 0:1.0.1-2.module+el8.9.0+19703+a1da72230:1.0.1-2.module+el8.9.0+19703+a1da7223
Red Hat:enterprise_linux:8::appstreamlibecap-debugsourcebefore 0:1.0.1-2.module+el8.9.0+19703+a1da72230:1.0.1-2.module+el8.9.0+19703+a1da7223

+46

Same product

squid-cache: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy
    56Plan
  • CVE-2023-49285Denial of Service in HTTP Message Processing in Squid
    56Plan
  • CVE-2021-31806An issue was discovered in Squid before 4.15 and 5.x before 5.0.6.
    55Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-54574Aug 1, 2025 · Squid's URN Handling can lead to Buffer Overflow
    46Plan
  • ← EarlierCVE-2025-59362Sep 26, 2025 · Squid through 7.1 mishandles ASN.1 encoding of long SNMP OIDs.
    16Monitor
  • Later →CVE-2026-32748Mar 25, 2026 · Squid has Denial of Service in ICP Response handling
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
squid-cache squid7.2 · descriptionVendor (CNA)
azl3 squid 6.13-1 on Azure Linux 3.06.13-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 squid 6.13-3 on Azure Linux 3.06.13-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:libecap1.0.1-2.module_el8.6.0+2741+01592ae8 · AlmaLinux:8Package registry (OSV)
almalinux:libecap-devel1.0.1-2.module_el8.6.0+2741+01592ae8 · AlmaLinux:8Package registry (OSV)
almalinux:squid7:4.15-10.module_el8.10.0+4055+645078d8.9 · AlmaLinux:8Package registry (OSV)
alpine:squid7.3-r0 · Alpine:v3.23Package registry (OSV)
debian:squid5.7-2+deb12u4 · Debian:12Package registry (OSV)
opensuse:squid6.10-150600.3.14.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:libecap0:1.0.1-2.module+el8.9.0+19703+a1da7223 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libecap-debuginfo0:1.0.1-2.module+el8.9.0+19703+a1da7223 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libecap-debugsource0:1.0.1-2.module+el8.9.0+19703+a1da7223 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libecap-devel0:1.0.1-2.module+el8.9.0+19703+a1da7223 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:squid7:4.15-10.module+el8.10.0+23592+d564ec65.9 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:squid-debuginfo7:4.15-10.module+el8.10.0+23592+d564ec65.9 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:squid-debugsource7:4.15-10.module+el8.10.0+23592+d564ec65.9 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:libecap0:1.0.1-2.module+el8.9.0+1437+df5ea8f0 · Rocky Linux:8Package registry (OSV)
rocky linux:squid7:4.15-10.module+el8.10.0+2080+49064dbd.9 · Rocky Linux:8Package registry (OSV)
suse:squid5.7-150400.3.38.2 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:squid6.10-150600.3.14.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub3 repositories2025-10-22 → 2025-11-25
Nuclei detection templateNuclei template CVE-2025-62168 —

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+4 d
  3. TodayNov 12, 2026+391 d
EPSS, last 120 days-2% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-209 · Generation of Error Message Containing Sensitive Information

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records