Vulnerability · CVE-2019-20454
An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode.
Published Feb 14, 2020 · catalog updated Nov 2, 2026 · An out-of-bounds read was
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2019-20454. EPSS is 1.56%. Act only if a listed version of An out-of-bounds read was is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (An out-of-bounds read was).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-58050 · Medium
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 1.56%
- Remediation
- Version ranges on file
- Affected products
- cpe fedoraproject/fedora · cpe pcre/pcre2 · cpe splunk/universal forwarder
An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode. Applications that use PCRE to parse untrusted input may be vulnerable to this flaw, which would allow an attacker to crash the application. The flaw occurs in do_extuni_no_utf in pcre2_jit_compile.c.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe fedoraproject/fedora31
- cpe pcre/pcre2< 10.34
- cpe splunk/universal forwarder9.1.0
- cpe splunk/universal forwarder< 8.2.12
- cpe splunk/universal forwarder< 9.0.6
How to fix CVE-2019-20454
Upgrade
CVE-2019-20454 lists a fix boundary at 10.34. Compare the installed build with that boundary before you change production.
Version check
Affected < 10.34
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2019-20454. EPSS is 1.56%. Act only if a listed version of An out-of-bounds read was is installed.
Which versions are affected?
Compare what you have installed with splunk/universal forwarder 9.1.0; splunk/universal forwarder < 8.2.12; splunk/universal forwarder < 9.0.6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-125: Out-of-bounds Read. EPSS 1.56%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Feb 14, 2020 · NIST NVD
Detected
An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode. Applications that use PCRE to parse untrusted input may be vulnerable to this flaw, which would allow an attacker to crash the application. The flaw occurs in do_extuni_no_utf in pcre2_jit_compile.c.
Nov 2, 2026 · NIST NVD
Updated
An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode. Applications that use PCRE to parse untrusted input may be vulnerable to this flaw, which would allow an attacker to crash the application. The flaw occurs in do_extuni_no_utf in pcre2_jit_compile.c.
Sources
- CVE.orgVulnerability recordCVE-2019-20454
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2019-20454
An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode. Applications that use PCRE to parse untrusted input may be vulnerable to this flaw, which would allow an attacker to crash t
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 4, 2026
- NIST NVDNov 2, 2026