{"id":"CVE-2016-8622","url":"https://www.cyber-defence.io/tools/cve/CVE-2016-8622","generatedAt":"2026-10-28T21:49:40.038Z","title":"The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`.","description":"The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus the length would get either just truncated or both truncated and turned negative. That could then lead to libcurl writing outside of its heap based buffer.","published":"2018-07-31T21:29:00.000Z","lastModified":"2026-06-17T00:54:38.000Z","status":"Modified","sourceIdentifier":"secalert@redhat.com","cvss":{"version":"3.0","score":9.8,"severity":"CRITICAL","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"},"cwe":["CWE-122","CWE-190","CWE-787"],"affected":["haxx/libcurl"],"epss":{"score":0.0467,"percentile":0.91716,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (4.67%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html","source":"secalert@redhat.com"},{"url":"http://www.securityfocus.com/bid/94105","tags":["Third Party Advisory","VDB Entry"],"source":"secalert@redhat.com"},{"url":"http://www.securitytracker.com/id/1037192","tags":["Third Party Advisory","VDB Entry"],"source":"secalert@redhat.com"},{"url":"https://access.redhat.com/errata/RHSA-2018:2486","tags":["Third Party Advisory"],"source":"secalert@redhat.com"},{"url":"https://access.redhat.com/errata/RHSA-2018:3558","source":"secalert@redhat.com"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8622","tags":["Issue Tracking","Patch","Third Party Advisory"],"source":"secalert@redhat.com"},{"url":"https://curl.haxx.se/docs/adv_20161102H.html","tags":["Patch","Vendor Advisory"],"source":"secalert@redhat.com"},{"url":"https://security.gentoo.org/glsa/201701-47","tags":["Third Party Advisory"],"source":"secalert@redhat.com"},{"url":"https://www.tenable.com/security/tns-2016-21","tags":["Third Party Advisory"],"source":"secalert@redhat.com"},{"url":"http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://www.securityfocus.com/bid/94105","tags":["Third Party Advisory","VDB Entry"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://www.securitytracker.com/id/1037192","tags":["Third Party Advisory","VDB Entry"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://access.redhat.com/errata/RHSA-2018:2486","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://access.redhat.com/errata/RHSA-2018:3558","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8622","tags":["Issue Tracking","Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://curl.haxx.se/docs/adv_20161102H.html","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.gentoo.org/glsa/201701-47","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://www.tenable.com/security/tns-2016-21","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2016-8622","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}