{"id":"CVE-2017-7186","url":"https://www.cyber-defence.io/tools/cve/CVE-2017-7186","generatedAt":"2026-10-28T23:08:28.844Z","title":"libpcre1 in PCRE 8.40 and libpcre2 in PCRE2 10.23 allow remote attackers to cause a denial of service (segmentation violation for read access, and application crash) by triggering an invalid Unicode property lookup.","description":"libpcre1 in PCRE 8.40 and libpcre2 in PCRE2 10.23 allow remote attackers to cause a denial of service (segmentation violation for read access, and application crash) by triggering an invalid Unicode property lookup.","published":"2017-03-20T00:59:00.000Z","lastModified":"2026-06-17T01:23:50.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.0","score":7.5,"severity":"HIGH","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"},"cwe":["CWE-119"],"affected":["pcre/pcre","pcre/pcre2"],"epss":{"score":0.05033,"percentile":0.92227,"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 (5.03%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"http://www.securityfocus.com/bid/97030","source":"cve@mitre.org"},{"url":"https://access.redhat.com/errata/RHSA-2018:2486","source":"cve@mitre.org"},{"url":"https://blogs.gentoo.org/ago/2017/03/14/libpcre-invalid-memory-read-in-match-pcre_exec-c/","tags":["Patch","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://bugs.exim.org/show_bug.cgi?id=2052","tags":["Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://security.gentoo.org/glsa/201710-09","source":"cve@mitre.org"},{"url":"https://security.gentoo.org/glsa/201710-25","source":"cve@mitre.org"},{"url":"https://vcs.pcre.org/pcre/code/trunk/pcre_internal.h?r1=1649&r2=1688&sortby=date","tags":["Patch"],"source":"cve@mitre.org"},{"url":"https://vcs.pcre.org/pcre/code/trunk/pcre_ucd.c?r1=1490&r2=1688&sortby=date","tags":["Patch"],"source":"cve@mitre.org"},{"url":"https://vcs.pcre.org/pcre2/code/trunk/src/pcre2_internal.h?r1=600&r2=670&sortby=date","tags":["Patch"],"source":"cve@mitre.org"},{"url":"https://vcs.pcre.org/pcre2/code/trunk/src/pcre2_ucd.c?r1=316&r2=670&sortby=date","tags":["Patch"],"source":"cve@mitre.org"},{"url":"http://www.securityfocus.com/bid/97030","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://access.redhat.com/errata/RHSA-2018:2486","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://blogs.gentoo.org/ago/2017/03/14/libpcre-invalid-memory-read-in-match-pcre_exec-c/","tags":["Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://bugs.exim.org/show_bug.cgi?id=2052","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.gentoo.org/glsa/201710-09","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.gentoo.org/glsa/201710-25","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://vcs.pcre.org/pcre/code/trunk/pcre_internal.h?r1=1649&r2=1688&sortby=date","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://vcs.pcre.org/pcre/code/trunk/pcre_ucd.c?r1=1490&r2=1688&sortby=date","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://vcs.pcre.org/pcre2/code/trunk/src/pcre2_internal.h?r1=600&r2=670&sortby=date","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://vcs.pcre.org/pcre2/code/trunk/src/pcre2_ucd.c?r1=316&r2=670&sortby=date","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-7186","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."}