CVE-2019-0539

HIGHNVD 7.58.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 83% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS: 83%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2019-0567, CVE-2019-0568.

CVSS v3
7.5
EG Score
8.9(high)
EG Risk
78(Track)
EG Risk 78/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
Severity89% × 45%
Exploitation83% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.6%
KEV
Not listed

Published

January 8, 2019

Last Modified

November 21, 2024

References (10)

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Microsoft.ChakraCore1.10.0 ... 1.8.5 (41 versions)1.11.5—

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 5× in last 7d / 17× 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:38 UTCEG score recompute▲ 1.40
  2. 2026-07-22 22:18 UTCEG score recompute▼ 1.50
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-15 16:55 UTCEPSS rescore
  7. 2026-07-15 01:56 UTCEPSS rescore
  8. 2026-07-12 05:43 UTCEPSS rescore
  9. 2026-07-09 19:06 UTCEPSS rescore
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-16 17:50 UTCEPSS rescore
  21. 2026-06-16 17:50 UTCEPSS rescore
  22. 2026-06-15 17:45 UTCEPSS rescore
  23. 2026-06-14 23:15 UTCEPSS rescore
  24. 2026-06-14 23:15 UTCEPSS rescore
  25. 2026-06-13 22:58 UTCEPSS rescore
Show 16 more
  1. 2026-06-12 23:09 UTCEPSS rescore
  2. 2026-06-12 23:09 UTCEPSS rescore
  3. 2026-06-10 22:16 UTCEPSS rescore
  4. 2026-06-10 13:19 UTCEPSS rescore
  5. 2026-06-08 14:14 UTCEPSS rescore
  6. 2026-06-07 15:22 UTCEPSS rescore
  7. 2026-06-07 15:22 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-06-05 22:45 UTCEPSS rescore
  11. 2026-06-05 22:45 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-27 23:42 UTCEG score recompute
  15. 2026-05-27 23:42 UTCVendor advisory
  16. 2026-05-27 13:38 UTCEPSS rescore

Publicly available exploits

(4 references)

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

  • GitHub PoC0x43434343/CVE-2019-0539
    First seen Jul 12, 2019

    R/W

    Open source ↗
  • Exploit-DBEDB-46485
    First seen Mar 4, 2019

    Microsoft Edge Chakra 1.11.4 - Read Permission via Type Confusion

    Open source ↗
  • Exploit-DBEDB-46204✓ verified
    First seen Jan 18, 2019

    Microsoft Edge Chakra - 'InitClass' Type Confusion

    Open source ↗
  • Exploit-DBEDB-46203✓ verified
    First seen Jan 18, 2019

    Microsoft Edge Chakra - 'NewScObjectNoCtor' or 'InitProto' Type Confusion

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-0539?
CVE-2019-0539 is a high vulnerability published on January 8, 2019. A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2019-0567, CVE-2019-0568.
When was CVE-2019-0539 disclosed?
CVE-2019-0539 was first published in the National Vulnerability Database on January 8, 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-0539 actively exploited?
CVE-2019-0539 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-0539?
CVE-2019-0539 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2019-0539?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0539, 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-0539

Explore →

Is Your Infrastructure Affected by CVE-2019-0539?

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

Start Free Scan →Browse All CVEs