CVE-2019-20838
No exploitation reported by the sources we read.
- Published2020-06-15
- Fixed in9.0.6 · 8.2.12
- WeaknessCWE-125
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
libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.
Timeline
dates in UTC- 2020-06-1517:15CVE 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-2019-20838?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-20838?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 |
|---|---|---|---|
| 9.0 | ≥ 9.0.0, < 9.0.6 | 9.0.6 | NVD |
| 8.2 | ≥ 8.2.0, < 8.2.12 | 8.2.12 | NVD |
| 9.1 | = 9.1.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 11.0 | < 11.0.1 | 11.0.1 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.43 | < 8.43 | 8.43 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- pcreAlmaLinux:8all versions · fixed in 8.42-6.el8and 5 other packages
Fix
- Update Splunk universal forwarder to 9.0.6 · 8.2.12
Advisories and patches
- bugs.gentoo.orgPatch
- support.apple.comVendor Advisory
- support.apple.comVendor Advisory
- www.pcre.orgRelease Notes · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2020-06-15
- Last Modified
- 2026-10-08
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-20838?
Is CVE-2019-20838 actively exploited?
What is the CVSS score for CVE-2019-20838?
Running pcre? Hear about its next vulnerability
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.