CVE-2021-41611

An issue was discovered in Squid 5.0.6 through 5.1.x before 5.2. When validating an origin server or peer certificate, Squid may incorrectly classify certain certificates as trusted. This problem allows a remote server to obtain security trust well improperly. This indication of trust may be passed along to clients, allowing access to unsafe or hijacked services.

Published: 2021-10-18 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-41611 is rated Moderate Risk (61.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.85%). EPSS rose +1.73% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-41611

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.12% 2.85% +1.73%
2 2026-05-27 2.16% 1.12% -1.04%
3 2025-11-21 — 2.16% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-41611

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2021-41611

OS Trackers for CVE-2021-41611

vendor priority summary link
alpine high CVE-2021-41611: 1 source package rows (squid); 12 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 5. https://security.alpinelinux.org/vuln/CVE-2021-41611
debian unimportant CVE-2021-41611 unimportant priority: Debian including 1 source packages (squid), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2021-41611
redhat high — https://access.redhat.com/security/cve/CVE-2021-41611
ubuntu medium CVE-2021-41611 medium priority: Ubuntu including 2 source packages (squid, squid3), 16 status rows across 8 suites (bionic, focal, hirsute, impish, jammy, trusty, upstream, xenial): DNE 8, not-affected 7, released 1. https://ubuntu.com/security/CVE-2021-41611

Affected software / configurations for CVE-2021-41611

Vendor Product Version Raw CPE
squid-cache squid >= 5.0.6, < 5.2 cpe:2.3:a:squid-cache:squid:*:*:*:*:*:*:*:*
fedoraproject fedora 35 cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*

References for CVE-2021-41611

cvelogic Threat Intelligence