| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE
|
Low
|
CVE-2026-89162
|
9/11/2026 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE
|
High
|
CVE-2026-89161
|
9/11/2026 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE
|
Low
|
CVE-2026-89160
|
9/11/2026 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE
|
Medium
|
CVE-2026-89158
|
9/11/2026 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE
|
Medium
|
CVE-2026-89157
|
9/11/2026 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE
|
Low
|
CVE-2026-89156
|
9/11/2026 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
PCRE2Project
|
Medium
|
CVE-2025-58050
- PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS
|
8/27/2025 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2022-41409
|
7/18/2023 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2022-1587
|
5/16/2022 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2022-1586
|
5/16/2022 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2020-14155
|
6/15/2020 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2019-20838
|
6/15/2020 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Medium
|
CVE-2019-20454
|
2/14/2020 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-8786
|
5/5/2017 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-8399
|
5/1/2017 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-7246
|
3/23/2017 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-7245
|
3/23/2017 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-7244
|
3/23/2017 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-7186
|
3/20/2017 |
| mingw64-i686-pcre2 |
conf-mingw-w64-pcre2-i686.1
|
n/a
|
Unknown
|
CVE-2017-6004
|
2/16/2017 |