CVE-2017-11839

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

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

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

Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709 allows an attacker to take control of an affected system, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11836, CVE-2017-11837, CVE-2017-11838, CVE-2017-11840, CVE-2017-11841, CVE-2017-11843, CVE-2017-11846, CVE-2017-11858, CVE-2017-11859, CVE-2017-11861, CVE-2017-11862, CVE-2017-11866, CVE-2017-11869, CVE-2017-11870, CVE-2017-11871, and CVE-2017-11873.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
99.1%
KEV
Not listed

Published

November 15, 2017

Last Modified

May 13, 2026

References (8)

Vendor Advisories for CVE-2017-11839(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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-07 13:42 UTCEPSS rescore
  2. 2026-07-05 02:27 UTCEPSS rescore
  3. 2026-07-04 06:28 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-27 03:05 UTCEPSS rescore
  8. 2026-06-25 13:47 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-22 14:23 UTCEPSS rescore
  13. 2026-06-22 14:23 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-18 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-14 23:14 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-10 22:15 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
Show 30 more
  1. 2026-06-07 15:22 UTCEPSS rescore
  2. 2026-06-06 13:45 UTCEPSS rescore
  3. 2026-06-06 13:45 UTCEPSS rescore
  4. 2026-06-05 22:44 UTCEPSS rescore
  5. 2026-06-05 06:08 UTCEPSS rescore
  6. 2026-06-05 06:08 UTCEPSS rescore
  7. 2026-06-02 20:11 UTCEPSS rescore
  8. 2026-06-02 20:11 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-05-31 22:28 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-27 13:38 UTCEPSS rescore
  14. 2026-05-27 13:38 UTCEPSS rescore
  15. 2026-05-26 13:42 UTCEPSS rescore
  16. 2026-05-26 13:42 UTCEPSS rescore
  17. 2026-05-26 07:17 UTCEPSS rescore
  18. 2026-05-26 07:17 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-22 08:05 UTCEG score recompute
  23. 2026-05-22 08:05 UTCVendor advisory
  24. 2026-05-22 08:05 UTCGHSA enrichment
  25. 2026-05-20 22:37 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 11:21 UTCEPSS rescore
  28. 2026-05-20 11:21 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore
  30. 2026-05-18 21:30 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-43180✓ verified
    First seen Nov 27, 2017

    Microsoft Edge Chakra JIT - 'BailOutOnTaggedValue' Bailouts Type Confusion

    Open source ↗

Frequently asked(5)

What is CVE-2017-11839?
CVE-2017-11839 is a high vulnerability published on November 15, 2017. Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709 allows an attacker to take control of an affected system, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is…
When was CVE-2017-11839 disclosed?
CVE-2017-11839 was first published in the National Vulnerability Database on November 15, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-11839 actively exploited?
CVE-2017-11839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-11839?
CVE-2017-11839 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-11839?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-11839, 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-2017-11839

Explore →

Is Your Infrastructure Affected by CVE-2017-11839?

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

Start Free Scan →Browse All CVEs