CVE-2018-6126

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekWeaponized
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 8%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

A precision error in Skia in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
70(Track)
EG Risk 70/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
Severity88% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
94.0%
KEV
Not listed

Published

January 9, 2019

Last Modified

November 21, 2024

References (26)

Vendor Advisories for CVE-2018-6126(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntufirefox (60.0.2+build1-0ubuntu0.17.10.1) @ artful2026-05-27ubuntu
redhatfirefox-0:60.1.0-4.el7_52018-06-28redhat
redhatfirefox-0:60.1.0-5.el62018-06-28redhat
redhatchromium-browser-0:67.0.3396.62-2.el6_92018-06-07redhat

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 13× in last 7d / 46× 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 14:15 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:37 UTCEG score recompute
  4. 2026-07-22 22:17 UTCEG score recompute
  5. 2026-07-22 14:05 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-21 00:17 UTCOSV refresh
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-19 14:28 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 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 01:56 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-12 05:43 UTCEPSS rescore
  20. 2026-07-09 19:06 UTCEPSS rescore
  21. 2026-07-08 15:11 UTCEPSS rescore
  22. 2026-07-08 15:11 UTCEPSS rescore
  23. 2026-07-07 13:42 UTCEPSS rescore
  24. 2026-07-07 13:42 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 64 more
  1. 2026-07-06 16:24 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-04 06:28 UTCEPSS rescore
  6. 2026-07-03 19:56 UTCOSV refresh
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-06-30 23:20 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-29 14:03 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-27 03:06 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
  26. 2026-06-18 17:50 UTCEPSS rescore
  27. 2026-06-18 17:50 UTCEPSS rescore
  28. 2026-06-17 17:50 UTCEPSS rescore
  29. 2026-06-16 17:50 UTCEPSS rescore
  30. 2026-06-16 17:50 UTCEPSS rescore
  31. 2026-06-15 17:45 UTCEPSS rescore
  32. 2026-06-15 07:43 UTCOSV refresh
  33. 2026-06-14 23:15 UTCEPSS rescore
  34. 2026-06-14 23:15 UTCEPSS rescore
  35. 2026-06-12 23:09 UTCEPSS rescore
  36. 2026-06-12 23:09 UTCEPSS rescore
  37. 2026-06-11 13:57 UTCEPSS rescore
  38. 2026-06-10 22:16 UTCEPSS rescore
  39. 2026-06-10 13:19 UTCEPSS rescore
  40. 2026-06-07 15:22 UTCEPSS rescore
  41. 2026-06-07 15:22 UTCEPSS rescore
  42. 2026-06-06 13:45 UTCEPSS rescore
  43. 2026-06-06 13:45 UTCEPSS rescore
  44. 2026-06-05 22:45 UTCEPSS rescore
  45. 2026-06-05 22:45 UTCEPSS rescore
  46. 2026-06-05 06:08 UTCEPSS rescore
  47. 2026-06-05 06:08 UTCEPSS rescore
  48. 2026-06-04 13:10 UTCEPSS rescore
  49. 2026-06-04 13:10 UTCEPSS rescore
  50. 2026-06-02 20:11 UTCEPSS rescore
  51. 2026-06-01 13:50 UTCEPSS rescore
  52. 2026-05-31 22:29 UTCEPSS rescore
  53. 2026-05-31 22:29 UTCEPSS rescore
  54. 2026-05-31 00:14 UTCEPSS rescore
  55. 2026-05-31 00:14 UTCEPSS rescore
  56. 2026-05-29 13:41 UTCEPSS rescore
  57. 2026-05-28 13:43 UTCEPSS rescore
  58. 2026-05-28 13:42 UTCEPSS rescore
  59. 2026-05-27 23:36 UTCEG score recompute
  60. 2026-05-27 23:36 UTCVendor advisory
  61. 2026-05-27 23:36 UTCGHSA enrichment
  62. 2026-05-26 11:15 UTCOSV refresh
  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 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-45098✓ verified
    First seen Jul 27, 2018

    Skia - Heap Overflow in SkScan::FillPath due to Precision Error

    Open source ↗

Frequently asked(5)

What is CVE-2018-6126?
CVE-2018-6126 is a high vulnerability published on January 9, 2019. A precision error in Skia in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.
When was CVE-2018-6126 disclosed?
CVE-2018-6126 was first published in the National Vulnerability Database on January 9, 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-2018-6126 actively exploited?
CVE-2018-6126 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-6126?
CVE-2018-6126 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2018-6126?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6126, 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-2018-6126

Explore →

Is Your Infrastructure Affected by CVE-2018-6126?

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

Start Free Scan →Browse All CVEs