CVE-2019-19203

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 4.1%, top 10% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

An issue was discovered in Oniguruma 6.x before 6.9.4_rc2. In the function gb18030_mbc_enc_len in file gb18030.c, a UChar pointer is dereferenced without checking if it passed the end of the matched string. This leads to a heap-based buffer over-read.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
—
EPSS
89.6%
KEV
Not listed

Published

November 21, 2019

Last Modified

November 21, 2024

References (12)

Vendor Advisories for CVE-2019-19203(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibonig-dev (5.9.6-1ubuntu0.1+esm3) @ xenial2026-05-27ubuntu
redhatoniguruma-0:6.8.2-2.1.el8_92024-02-20redhat
redhatoniguruma-0:6.8.2-2.1.el8_82024-01-30redhat
redhatoniguruma-0:6.8.2-2.1.el8_62024-01-25redhat
redhatrh-php73-php-0:7.3.20-1.el72020-12-01redhat
redhatphp:7.3-8020020200715124551.ceb1cf902020-09-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:23 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-20 01:46 UTCOSV refresh
  8. 2026-07-19 14:28 UTCEPSS rescore
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-18 10:01 UTCEPSS rescore
  13. 2026-07-16 16:59 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-15 16:55 UTCEPSS rescore
  16. 2026-07-15 16:55 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-12 05:43 UTCEPSS rescore
  19. 2026-07-12 05:43 UTCEPSS rescore
  20. 2026-07-11 08:24 UTCEPSS rescore
  21. 2026-07-11 08:24 UTCEPSS rescore
  22. 2026-07-09 19:06 UTCEPSS rescore
  23. 2026-07-08 15:11 UTCEPSS rescore
  24. 2026-07-07 13:43 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 64 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-05 02:27 UTCEPSS rescore
  4. 2026-07-04 06:28 UTCEPSS rescore
  5. 2026-07-02 16:54 UTCOSV refresh
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-28 04:54 UTCEPSS rescore
  10. 2026-06-28 04:54 UTCEPSS rescore
  11. 2026-06-27 03:06 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:03 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
  26. 2026-06-15 17:45 UTCEPSS rescore
  27. 2026-06-14 23:15 UTCEPSS rescore
  28. 2026-06-14 23:15 UTCEPSS rescore
  29. 2026-06-14 14:13 UTCOSV refresh
  30. 2026-06-13 22:58 UTCEPSS rescore
  31. 2026-06-12 23:09 UTCEPSS rescore
  32. 2026-06-11 13:58 UTCEPSS rescore
  33. 2026-06-10 22:16 UTCEPSS rescore
  34. 2026-06-10 13:19 UTCEPSS rescore
  35. 2026-06-08 14:15 UTCEPSS rescore
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-07 15:23 UTCEPSS rescore
  38. 2026-06-06 13:45 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-05 22:45 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 06:08 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-02 20:11 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-01 13:50 UTCEPSS rescore
  49. 2026-06-01 13:50 UTCEPSS rescore
  50. 2026-05-31 22:29 UTCEPSS rescore
  51. 2026-05-31 22:29 UTCEPSS rescore
  52. 2026-05-31 00:14 UTCEPSS rescore
  53. 2026-05-31 00:14 UTCEPSS rescore
  54. 2026-05-29 13:42 UTCEPSS rescore
  55. 2026-05-28 13:43 UTCEPSS rescore
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-27 11:22 UTCEG score recompute
  58. 2026-05-27 11:22 UTCVendor advisory
  59. 2026-05-27 11:22 UTCGHSA enrichment
  60. 2026-05-26 13:42 UTCEPSS rescore
  61. 2026-05-26 13:42 UTCEPSS rescore
  62. 2026-05-26 07:17 UTCEPSS rescore
  63. 2026-05-26 07:17 UTCEPSS rescore
  64. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCManhNDd/CVE-2019-19203
    First seen Nov 21, 2019

    Heap-buffer-overflow in Oniguruma (function gb18030_mbc_enc_len)

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-19203?
CVE-2019-19203 is a high vulnerability published on November 21, 2019. An issue was discovered in Oniguruma 6.x before 6.9.4rc2. In the function gb18030mbcenclen in file gb18030.c, a UChar pointer is dereferenced without checking if it passed the end of the matched string. This leads to a heap-based buffer over-read.
When was CVE-2019-19203 disclosed?
CVE-2019-19203 was first published in the National Vulnerability Database on November 21, 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-19203 actively exploited?
CVE-2019-19203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-19203?
CVE-2019-19203 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-19203?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-19203, 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

Explore the affected products and dependency analysis for CVE-2019-19203

Explore →

Is Your Infrastructure Affected by CVE-2019-19203?

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

Start Free Scan →Browse All CVEs