PCRE
- Products in analyzed data
- 1
- Catalog vulnerabilities
- 64
Severity across 7 analyzed records
Verify to analyze this security profile
A short verification protects source data and prevents automated AI requests.
en
Severity across 7 analyzed records
A short verification protects source data and prevents automated AI requests.
As of 09/11/2026, PCRE recorded 7 security vulnerabilities in the last 90 days across 1 products, including 2 rated High or above and 0 known exploited vulnerabilities (KEV) that should be prioritized for immediate remediation.
Over the last 90 days, PCRE2 had the most security vulnerabilities in the PCRE ecosystem, with 7 vulnerabilities—approximately 100% of the provider's total vulnerabilities during this period.
| CVE | Exploitation status | Fix | Affected product | Published | Severity |
|---|---|---|---|---|---|
CVE-2026-89162CVE-2026-89162 | Exploitation statusNot confirmed | FixYes | Affected productPCRE2 | Published09/11/2026 | SeverityLow |
CVE-2026-89161CVE-2026-89161 | Exploitation statusNot confirmed | FixYes | Affected productPCRE2 | Published09/11/2026 | SeverityHigh |
CVE-2026-89160CVE-2026-89160 | Exploitation statusNot confirmed | FixYes | Affected productPCRE2 | Published09/11/2026 | SeverityLow |
CVE-2026-89158CVE-2026-89158 | Exploitation statusNot confirmed | FixYes | Affected productPCRE2 | Published09/11/2026 | SeverityMedium |
CVE-2026-89157CVE-2026-89157 | Exploitation statusNot confirmed | FixYes | Affected productPCRE2 | Published09/11/2026 | SeverityMedium |
CVE-2026-89156CVE-2026-89156 | Exploitation statusNot confirmed | FixYes | Affected productPCRE2 | Published09/11/2026 | SeverityLow |
CVE-2026-86145CVE-2026-86145 | Exploitation statusNot known exploited | FixYes | Affected productPCRE2 | Published09/05/2026 | SeverityHigh |
CVE-2025-58050PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS | Exploitation statusPublic exploit | FixYes | Affected productpcre2 | Published08/27/2025 | SeverityMedium |
CVE-2022-41409CVE-2022-41409 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published07/18/2023 | SeverityUnknown |
CVE-2022-1587CVE-2022-1587 | Exploitation statusNot confirmed | FixNot confirmed | Affected productpcre2 | Published05/16/2022 | SeverityUnknown |
CVE-2022-1586CVE-2022-1586 | Exploitation statusNot confirmed | FixNot confirmed | Affected productpcre2 | Published05/16/2022 | SeverityUnknown |
CVE-2019-20838CVE-2019-20838 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published06/15/2020 | SeverityUnknown |
CVE-2020-14155CVE-2020-14155 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published06/15/2020 | SeverityUnknown |
CVE-2019-20454CVE-2019-20454 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/14/2020 | SeverityMedium |
CVE-2015-2326CVE-2015-2326 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/14/2020 | SeverityUnknown |
CVE-2015-2325CVE-2015-2325 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/14/2020 | SeverityUnknown |
CVE-2017-16231CVE-2017-16231 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published03/17/2019 | SeverityMedium |
CVE-2017-11164CVE-2017-11164 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/11/2017 | SeverityUnknown |
CVE-2017-8786CVE-2017-8786 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/05/2017 | SeverityUnknown |
CVE-2017-8399CVE-2017-8399 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/01/2017 | SeverityUnknown |
CVE-2017-7245CVE-2017-7245 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/23/2017 | SeverityUnknown |
CVE-2017-7244CVE-2017-7244 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/23/2017 | SeverityUnknown |
CVE-2017-7246CVE-2017-7246 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/23/2017 | SeverityUnknown |
CVE-2017-7186CVE-2017-7186 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/20/2017 | SeverityUnknown |
CVE-2017-6004CVE-2017-6004 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/16/2017 | SeverityUnknown |
CVE-2015-3210CVE-2015-3210 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/13/2016 | SeverityUnknown |
CVE-2015-5073CVE-2015-5073 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/13/2016 | SeverityUnknown |
CVE-2015-3217CVE-2015-3217 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/13/2016 | SeverityUnknown |
CVE-2014-9769CVE-2014-9769 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/28/2016 | SeverityUnknown |
CVE-2016-3191CVE-2016-3191 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/17/2016 | SeverityUnknown |
CVE-2016-1283CVE-2016-1283 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/03/2016 | SeverityUnknown |
CVE-2015-8392CVE-2015-8392 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8382CVE-2015-8382 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-2327CVE-2015-2327 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-2328CVE-2015-2328 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8380CVE-2015-8380 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8395CVE-2015-8395 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8381CVE-2015-8381 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8384CVE-2015-8384 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8385CVE-2015-8385 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8388CVE-2015-8388 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8394CVE-2015-8394 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8391CVE-2015-8391 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8393CVE-2015-8393 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8390CVE-2015-8390 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8386CVE-2015-8386 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8383CVE-2015-8383 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8389CVE-2015-8389 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2015-8387CVE-2015-8387 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2015 | SeverityUnknown |
CVE-2014-8964CVE-2014-8964 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/16/2014 | SeverityUnknown |
CVE-2008-2371CVE-2008-2371 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/07/2008 | SeverityUnknown |
CVE-2008-0674CVE-2008-0674 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/18/2008 | SeverityUnknown |
CVE-2006-7230CVE-2006-7230 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/15/2007 | SeverityUnknown |
CVE-2005-4872CVE-2005-4872 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/14/2007 | SeverityUnknown |
CVE-2006-7227CVE-2006-7227 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/14/2007 | SeverityUnknown |
CVE-2006-7228CVE-2006-7228 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/14/2007 | SeverityUnknown |
CVE-2007-4767CVE-2007-4767 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2007-1662CVE-2007-1662 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2007-1659CVE-2007-1659 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2007-1661CVE-2007-1661 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2007-4766CVE-2007-4766 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2007-4768CVE-2007-4768 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2007-1660CVE-2007-1660 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2007 | SeverityUnknown |
CVE-2005-2491CVE-2005-2491 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published08/22/2005 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan