CVE-2018-5163

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 8.1Exploit: NoneExposed: 0

A fix is available — apply it.

If a malicious attacker has used another vulnerability to gain full control over a content process, they may be able to replace the alternate data resources stored in the JavaScript Start-up Bytecode Cache (JSBC) for other JavaScript code. If the parent process then runs this replaced code, the executed script would be run with the parent process' privileges, escaping the sandbox on content processes. This vulnerability affects Firefox < 60.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
79.6%
KEV
Not listed

Published

June 11, 2018

Last Modified

November 21, 2024

References (10)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntufirefox-testsuite (60.0+build2-0ubuntu0.16.04.1) @ xenial2026-05-28ubuntu

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2018-5163?
CVE-2018-5163 is a high vulnerability published on June 11, 2018. If a malicious attacker has used another vulnerability to gain full control over a content process, they may be able to replace the alternate data resources stored in the JavaScript Start-up Bytecode Cache (JSBC) for other JavaScript code. If the parent process then runs this replaced code, the…
When was CVE-2018-5163 disclosed?
CVE-2018-5163 was first published in the National Vulnerability Database on June 11, 2018, 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-5163 actively exploited?
CVE-2018-5163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-5163?
CVE-2018-5163 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2018-5163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-5163, 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-5163

Explore →

Is Your Infrastructure Affected by CVE-2018-5163?

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

Start Free Scan →Browse All CVEs