CVE-2011-3596 in the critical feed json
Polipo before 1.0.4.1 suffers from a DoD vulnerability via specially-crafted HTTP POST / PUT request.
published 2019-11-25 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3555
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.1%
- EPSS 11.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Polipo before 1.0.4.1 suffers from a DoD vulnerability via specially-crafted HTTP POST / PUT request.
Patch / fix
- polipo_project polipo 1.0.4.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-3596 updated cvss 3.3
polipo: Assertion failure by processing certain HTTP POST / PUT requests
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- First public exploit (EDB-36198)
- Published
Exploit prediction
11.05% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-36198 Polipo 1.0.4.1 - POST/PUT HTTP Header Processing Denial of Service dos, 2011-10-01
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- polipo polipo
Classification
- Weakness
-
- CWE-617 Reachable Assertion
References
-
security-tracker.debian.org
/tracker/CVE-2011-3596
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2011-3596
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2011-3596
third-party-advisory
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=644289
third-party-advisory
Sources
- CVE List CVE-2011-3596
- NVD CVE-2011-3596
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.