CVE-2019-12526: An issue was discovered in Squid before 4.9.
Noroxi assessment
Priority: Plan (action score 45/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: 20.2% (FIRST EPSS); higher than 97.4% 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.
- Fixed version: libecap (AlmaLinux:8) 1.0.1-2.module_el8.6.0+2741+01592ae8; libecap-devel (AlmaLinux:8) 1.0.1-2.module_el8.6.0+2741+01592ae8; squid (Debian:10) 4.6-1+deb10u2.
Add it to your regular patch cycle. Upgrade to libecap (AlmaLinux:8) 1.0.1-2.module_el8.6.0+2741+01592ae8; libecap-devel (AlmaLinux:8) 1.0.1-2.module_el8.6.0+2741+01592ae8; squid (Debian:10) 4.6-1+deb10u2 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 before 4.9. URN response handling in Squid suffers from a heap-based buffer overflow. When receiving data from a remote server in response to an URN request, Squid fails to ensure that the response can fit within the buffer. This leads to attacker controlled data overflowing in the heap.
- Published
- Nov 26, 2019
- Updated
- Jun 16, 2026
- EPSS
- 20.2% · 97th percentile
- CWE
- CWE-787
Report tools
Action score
45
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 6 / 30 · 20.2%
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 |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.04
- canonical ubuntu linux19.10
- debian debian linux10.0
- debian debian linux8.0
- debian debian linux9.0
- fedoraproject fedora30
- fedoraproject fedora31
- opensuse leap15.0
- squid-cache squid3.0 and later · up to 3.5.28 inclusive
- squid-cache squid4.0 and later · up to 4.8 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | libecap | before 1.0.1-2.module_el8.6.0+2741+01592ae8 | 1.0.1-2.module_el8.6.0+2741+01592ae8 |
| AlmaLinux:8 | libecap-devel | before 1.0.1-2.module_el8.6.0+2741+01592ae8 | 1.0.1-2.module_el8.6.0+2741+01592ae8 |
| Debian:10 | squid | before 4.6-1+deb10u2 | 4.6-1+deb10u2 |
| Debian:12 | squid | before 4.9-1 | 4.9-1 |
| Debian:8 | squid3 | before 3.4.8-6+deb8u9 | 3.4.8-6+deb8u9 |
| Debian:9 | squid3 | before 3.5.23-5+deb9u2 | 3.5.23-5+deb9u2 |
| openSUSE:Leap 15.0 | squid | before 4.9-lp150.13.1 | 4.9-lp150.13.1 |
| openSUSE:Leap 15.1 | squid | before 4.9-lp151.2.7.1 | 4.9-lp151.2.7.1 |
| openSUSE:Tumbleweed | squid | before 4.16-1.5 | 4.16-1.5 |
| Red Hat:enterprise_linux:8::appstream | libecap | before 0:1.0.1-2.module+el8.1.0+4044+36416a77 | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| Red Hat:enterprise_linux:8::appstream | libecap-debuginfo | before 0:1.0.1-2.module+el8.1.0+4044+36416a77 | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| Red Hat:enterprise_linux:8::appstream | libecap-debugsource | before 0:1.0.1-2.module+el8.1.0+4044+36416a77 | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| Red Hat:enterprise_linux:8::appstream | libecap-devel | before 0:1.0.1-2.module+el8.1.0+4044+36416a77 | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| Red Hat:enterprise_linux:8::appstream | squid | before 7:4.11-3.module+el8.3.0+7851+7808b5f9 | 7:4.11-3.module+el8.3.0+7851+7808b5f9 |
| Red Hat:enterprise_linux:8::appstream | squid-debuginfo | before 7:4.11-3.module+el8.3.0+7851+7808b5f9 | 7:4.11-3.module+el8.3.0+7851+7808b5f9 |
| Red Hat:enterprise_linux:8::appstream | squid-debugsource | before 7:4.11-3.module+el8.3.0+7851+7808b5f9 | 7:4.11-3.module+el8.3.0+7851+7808b5f9 |
| Rocky Linux:8 | libecap | before 0:1.0.1-2.module+el8.4.0+404+316a0dc5 | 0:1.0.1-2.module+el8.4.0+404+316a0dc5 |
| SUSE:HPE Helion OpenStack 8 | squid | before 3.5.21-26.20.1 | 3.5.21-26.20.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 | squid | before 4.9-5.11.1 | 4.9-5.11.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | squid3 | before 3.1.23-8.16.37.12.1 | 3.1.23-8.16.37.12.1 |
| SUSE:Linux Enterprise Server 12 SP5 | squid | before 4.9-4.3.2 | 4.9-4.3.2 |
Same product
squid-cache: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy56Plan
- CVE-2023-49285Denial of Service in HTTP Message Processing in Squid56Plan
- 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-2019-12854Aug 15, 2019 · Due to incorrect string termination, Squid cachemgr.cgi 4.0 through 4.7 may access unallocated memory.34Monitor
- ← EarlierCVE-2019-12523Nov 26, 2019 · An issue was discovered in Squid before 4.9.37Monitor
- Later →CVE-2019-18676Nov 26, 2019 · An issue was discovered in Squid 3.x and 4.x through 4.8.33Monitor
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 |
|---|---|---|
| almalinux:libecap | 1.0.1-2.module_el8.6.0+2741+01592ae8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libecap-devel | 1.0.1-2.module_el8.6.0+2741+01592ae8 · AlmaLinux:8 | Package registry (OSV) |
| debian:squid | 4.9-1 · Debian:12 | Package registry (OSV) |
| debian:squid3 | 3.4.8-6+deb8u9 · Debian:8 | Package registry (OSV) |
| opensuse:squid | 4.9-lp150.13.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| red hat:libecap | 0:1.0.1-2.module+el8.1.0+4044+36416a77 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libecap-debuginfo | 0:1.0.1-2.module+el8.1.0+4044+36416a77 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libecap-debugsource | 0:1.0.1-2.module+el8.1.0+4044+36416a77 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libecap-devel | 0:1.0.1-2.module+el8.1.0+4044+36416a77 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:squid | 7:4.11-3.module+el8.3.0+7851+7808b5f9 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:squid-debuginfo | 7:4.11-3.module+el8.3.0+7851+7808b5f9 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:squid-debugsource | 7:4.11-3.module+el8.3.0+7851+7808b5f9 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:libecap | 0:1.0.1-2.module+el8.4.0+404+316a0dc5 · Rocky Linux:8 | Package registry (OSV) |
| suse:squid | 4.9-5.11.1 · SUSE:Linux Enterprise Module for Server Applications 15 | Package registry (OSV) |
| suse:squid3 | 3.1.23-8.16.37.12.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
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.
- 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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- bugzilla.suse.com/show_bug.cgi?id=1156326
- lists.debian.org/debian-lts-announce/2019/12/msg00011.html
- lists.debian.org/debian-lts-announce/2020/07/msg00009.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MTM74TU2BSLT5B3H4F3UDW53672NVLMC/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UEMOYTMCCFWK5NOXSXEIH5D2VGWVXR67/
- security.gentoo.org/glsa/202003-34
- usn.ubuntu.com/4213-1/
- www.debian.org/security/2020/dsa-4682
Vendor advisories and official records. Exploit/PoC links are deliberately left out.