PCRE before 8.36 mishandles the /(((a\2)|(a*)\g<-1>))*/ pattern and related patterns with certain internal recursive back references, which allows remote attackers to cause a denial of service (segmentation fault) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade pcre | Aug 30, 2017 | Dec 1, 2015 |
| Debian | — | Upgrade pcre3 | Jul 30, 2024 | Dec 2, 2015 |
| F5 Big Ip | — | Update F5 BIG-IP to the latest version | Jun 17, 2026 | Feb 4, 2016 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jul 11, 2014 |
| Suse | — | Upgrade libpcre16-0Upgrade sles12-docker-imageUpgrade pcre-develUpgrade libpcre1-32bitUpgrade libpcre1Upgrade libpcrecpp0Upgrade pcre-toolsUpgrade pcre-devel-staticUpgrade libpcreposix0Upgrade libpcrecpp0-32bitUpgrade sles12sp1-docker-image | Dec 3, 2016 | Dec 1, 2015 |
| Ubuntu | — | Upgrade libpcre3 | Apr 4, 2016 | Dec 1, 2015 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub