CVE-2016-1283
No exploitation reported by the sources we read.
- Published2016-01-03
- Fixed in7.1.11 · 7.0.25 · 5.6.32
- WeaknessCWE-119
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The pcre_compile2 function in pcre_compile.c in PCRE 8.38 mishandles the /((?:F?+(?:^(?(R)a+\"){99}-))(?J)(?'R'(?'R'<((?'RR'(?'R'\){97)?J)?J)(?'R'(?'R'\){99|(:(?|(?'R')(\k'R')|((?'R')))H'R'R)(H'R))))))/ pattern and related patterns with named subgroups, which allows remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.
Timeline
dates in UTC- 2016-01-0300:59CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-1283?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-1283?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.1 | ≥ 7.1.0, < 7.1.11 | 7.1.11 | NVD |
| 7.0 | ≥ 7.0.0, < 7.0.25 | 7.0.25 | NVD |
| 5.6 | ≥ 5.6.0, < 5.6.32 | 5.6.32 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 22.x | = 22 | no fix published | NVD |
| 23.x | = 23 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 11.3 | = 11.3 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update PHP to 7.1.11 · 7.0.25 · 5.6.32
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-119read 2026-10-23
- FIRST EPSSEPSS score7.8 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-01-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-1283?
Is CVE-2016-1283 actively exploited?
What is the CVSS score for CVE-2016-1283?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.