Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-7186: libpcre1 in PCRE 8.40 and libpcre2 in PCRE2 10.23 allow remote attackers to cause a denial of service (segment

54
This month
HIGH 7.5REMOTEDOWNGRADEDOWNGRADE

CVE-2017-7186 is a high-severity flaw (CVSS 7.5) affecting pcre, pcre2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

libpcre1 in PCRE 8.40 and libpcre2 in PCRE2 10.23 allow remote attackers to cause a denial of service (segmentation violation for read access, and application crash) by triggering an invalid Unicode property lookup.

Why this priority

  • High severity
  • EPSS top 8%: very likely to be exploited
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance5.0% (top 8%)
CISA exploited listNo
WeaknessCWE-119
Published2017-03-20
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: pcre

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

pcre pcre DOWNGRADE
Affected: 8.40
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.40
1. Check installed version
apt-cache policy pcre || rpm -q pcre || pcre --version
2. No fixed release: DOWNGRADE to a release before 8.40 (Debian / Ubuntu)
apt-cache madison pcre sudo apt install pcre=<VERSION_BEFORE_8.40> sudo apt-mark hold pcre
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list pcre sudo dnf downgrade pcre-<VERSION_BEFORE_8.40> sudo dnf versionlock add pcre
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
pcre pcre2 DOWNGRADE
Affected: 10.23
Fixed in: no fixed release known
Safe to downgrade to: a release before 10.23
1. Check installed version
apt-cache policy pcre2 || rpm -q pcre2 || pcre2 --version
2. No fixed release: DOWNGRADE to a release before 10.23 (Debian / Ubuntu)
apt-cache madison pcre2 sudo apt install pcre2=<VERSION_BEFORE_10.23> sudo apt-mark hold pcre2
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list pcre2 sudo dnf downgrade pcre2-<VERSION_BEFORE_10.23> sudo dnf versionlock add pcre2
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-7186?

pcre: downgrade or apply the listed mitigation; pcre2: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-7186 being exploited?

CVE-2017-7186 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-7186 affect?

CVE-2017-7186 affects pcre, pcre2. Severity is high (CVSS 7.5). libpcre1 in PCRE 8.40 and libpcre2 in PCRE2 10.23 allow remote attackers to cause a denial of service (segmentation violation for read access, and application crash) by triggering an invalid Unicode property lookup.

How urgent is CVE-2017-7186?

Priority 54/100. High severity; EPSS top 8%: very likely to be exploited; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.