LiveActive security incident?Get immediate response
CVE Record

CVE-2016-3191: The compile_branch function in pcre_compile.c in PCRE 8.x before 8.39 and pcre2_compile.c in PCRE2 before 1...

The compile_branch function in pcre_compile.c in PCRE 8.x before 8.39 and pcre2_compile.c in PCRE2 before 10.22 mishandles patterns containing an (*ACCEPT) substring in conjunction with nested parentheses, which allows remote attackers to execute arbitrary code or cause a denial of service (stack-based buffer overflow) via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror, aka ZDI-CAN-3542.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2016-3191 is a flaw in the PCRE regular expression compiler. A specially crafted regular expression can corrupt stack memory when affected PCRE/PCRE2 versions parse it. Systems are most at risk when they compile regex patterns supplied by users, files, mail, scripts, or web content. Impact can include crash or arbitrary code execution. Exposure depends on whether software uses vulnerable PCRE/PCRE2 and compiles attacker-controlled regular expressions. The source bundle cites Konqueror JavaScript RegExp handling as a demonstration and includes vendor references from Red Hat, Debian, Oracle, IBM, Blue Coat, Tenable, and Exim. Prioritize remediation where internet-facing or content-processing systems compile untrusted regular expressions. Business urgency is lower for systems using PCRE only with trusted, static patterns, but inventory is important because PCRE is widely embedded. Mitigation focus: Upgrade PCRE to 8.39 or later where PCRE 8.x is used.; Upgrade PCRE2 to 10.22 or later where PCRE2 is used.; Apply relevant vendor security updates from affected operating system or product suppliers..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-3191 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.