CVE-2019-12798

CRITICALNVD 9.89.8—

9.8

An issue was discovered in Artifex MuJS 1.0.5. regcompx in regexp.c does not restrict regular expression program size, leading to an overflow of the parsed syntax list size.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 63.0%
KEV: Not listed

Published

June 13, 2019

Last Modified

November 21, 2024

References (4)

cve@mitrehttp://git.ghostscript.com/?p=mujs.git%3Bh=7f50591861525f76e3ec7a63392656ff8c030af9
cve@mitrehttp://www.securityfocus.com/bid/108774
af854a3a-2127-422b-91ae-364da2661108http://git.ghostscript.com/?p=mujs.git%3Bh=7f50591861525f76e3ec7a63392656ff8c030af9
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/108774

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-185Incorrect Regular Expression

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 18:23 UTCEG score recompute
2026-05-27 18:23 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-12798?

CVE-2019-12798 is a critical vulnerability published on June 13, 2019. An issue was discovered in Artifex MuJS 1.0.5. regcompx in regexp.c does not restrict regular expression program size, leading to an overflow of the parsed syntax list size.

When was CVE-2019-12798 disclosed?

CVE-2019-12798 was first published in the National Vulnerability Database on June 13, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-12798 actively exploited?

CVE-2019-12798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 63.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-12798?

CVE-2019-12798 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2019-12798?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-12798, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-12798

Explore →

Is Your Infrastructure Affected by CVE-2019-12798?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

Frequently asked(5)

What is CVE-2019-12798?

When was CVE-2019-12798 disclosed?

Is CVE-2019-12798 actively exploited?

What is the CVSS score of CVE-2019-12798?

CVE-2019-12798 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2019-12798?

CVE-2019-12798

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-12798?

CVE-2019-12798

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-12798?

Published

Last Modified

References (4)

Frequently asked(5)

Published

Last Modified

References (4)

Frequently asked(5)