CVE-2019-19012

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 10.5%, top 5% 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
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 11%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or information disclosure, or possibly have unspecified other impact, via a crafted regular expression.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
65(Track*)
EG Risk 65/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
95.3%
KEV
Not listed

Published

November 17, 2019

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jun 22, 2026
🔬 Proof of concept available. Patch available. Sources: github_release.
generic🟡 PoC Available

GitHub - tarantula-team/CVE-2019-19012: An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read · GitHub

https://github.com/tarantula-team/CVE-2019-19012
github_release Patch Available

6.9.4 Release Candidate 2

Patch available: kkos/oniguruma v6.9.4_rc2 (pre-release)

https://github.com/kkos/oniguruma/releases/tag/v6.9.4_rc2
generic

Integer overflow related to reg->dmax in search_in_range (regexec.c) · Issue #164 · kkos/oniguruma · GitHub

https://github.com/kkos/oniguruma/issues/164
generic

[SECURITY] Fedora 30 Update: oniguruma-6.9.2-4.fc30 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V3MBNW6Z4DOXSCNWGBLQ7OA3OGUJ44WL/
generic

[SECURITY] Fedora 31 Update: oniguruma-6.9.4-1.fc31 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NO267PLHGYZSWX3XTRPKYBKD4J3YOU5V/
generic Patch Available

[SECURITY] [DLA 2020-1] libonig security update

https://lists.debian.org/debian-lts-announce/2019/12/msg00002.html

Vendor Advisories for CVE-2019-19012(3)

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.1-1ubuntu1.1+esm2) @ trusty2026-05-27ubuntu
ubuntulibonig-dev (6.7.0-1ubuntu0.1~esm2) @ bionic2026-05-27ubuntu
redhatruby:2.5-8100020250506105643.489197e62025-05-14redhat
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

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(2)

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

Additional Vendor Advisories

(3)

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

    Integer overflow in Oniguruma

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-19012?
CVE-2019-19012 is a critical vulnerability published on November 17, 2019. An integer overflow in the searchinrange function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or…
When was CVE-2019-19012 disclosed?
CVE-2019-19012 was first published in the National Vulnerability Database on November 17, 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-19012 actively exploited?
CVE-2019-19012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-19012?
CVE-2019-19012 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-19012?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-19012, 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-19012

Explore →

Is Your Infrastructure Affected by CVE-2019-19012?

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

Start Free Scan →Browse All CVEs