An issue was discovered in Squid 4.9 through 4.17 and 5.0.6 through 5.6.
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77.9% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a n/a 5.7.
Low priority for now. Upgrade to n/a n/a 5.7 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
An issue was discovered in Squid 4.9 through 4.17 and 5.0.6 through 5.6. Due to inconsistent handling of internal URIs, there can be Exposure of Sensitive Information about clients using the proxy via an HTTPS request to an internal cache manager URL. This is fixed in 5.7.
- Published
- Dec 25, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-697
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| squid-cache | squid | cpe:2.3:a:squid-cache:squid |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- squid-cache squid4.9 and later · up to 4.17 inclusive
- squid-cache squid5.0.6 and later · before 5.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.19 | squid | from 4.9 · before 5.7-r0 | 5.7-r0 |
| Debian:10 | squid | before 4.6-1+deb10u8 | 4.6-1+deb10u8 |
| Debian:11 | squid | before 4.13-10+deb11u2 | 4.13-10+deb11u2 |
| Debian:12 | squid | before 5.7-1 | 5.7-1 |
| openSUSE:Tumbleweed | squid | before 5.7-2.1 | 5.7-2.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP3 | squid | before 4.17-150000.5.35.1 | 4.17-150000.5.35.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP3 | squid | before 4.17-150000.5.35.1 | 4.17-150000.5.35.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP4 | squid | before 5.7-150400.3.6.1 | 5.7-150400.3.6.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP4 | squid | before 5.7-150400.3.6.1 | 5.7-150400.3.6.1 |
| SUSE:Linux Enterprise Server 12 SP5 | squid | before 4.17-4.27.1 | 4.17-4.27.1 |
| SUSE:OpenStack Cloud 9 | squid | before 3.5.21-26.38.1 | 3.5.21-26.38.1 |
Same product
squid-cache: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-46847Squid: denial of service in http digest authentication57Plan
- CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy56Plan
- CVE-2023-49285Denial of Service in HTTP Message Processing in Squid56Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-41611Oct 18, 2021 · An issue was discovered in Squid 5.0.6 through 5.1.x before 5.2.31Monitor
- ← EarlierCVE-2021-46784Jul 17, 2022 · In Squid 3.x through 3.5.28, 4.x through 4.17, and 5.x before 5.6, due to improper buffer management, a Denial of Service can occur when pro28Monitor
- Later →CVE-2022-41318Dec 25, 2022 · A buffer over-read was discovered in libntlmauth in Squid 2.5 through 5.6.35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a n/a | 5.7 · description | Vendor (CNA) |
| alpine:squid | 5.7-r0 · Alpine:v3.19 | Package registry (OSV) |
| debian:squid | 5.7-1 · Debian:12 | Package registry (OSV) |
| opensuse:squid | 5.7-150400.3.6.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:squid | 5.7-150400.3.6.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-697 · Incorrect ComparisonCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Command DelimitersCAPEC-15likelihood: High · High
- Flash InjectionCAPEC-182likelihood: High · Medium
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Leading 'Ghost' Character Sequences to Bypass Input FiltersCAPEC-3likelihood: Medium · Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.