CVE-2017-16231

What it is

In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2019-03-21 15:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:09 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 5.5 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2019-03-21 15:59 UTC

Last modified

2026-06-17 01:09 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-119 · Buffer errors

Record status

Modified

Affected

• Pcre 8.41

Attack profile CVSS 3.1 · 5.5

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-16231.md and follow it. Check whether this project is affected by CVE-2017-16231. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge