CVE-2017-5753

CRITICALNVD 5.69.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 94% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 5.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 262 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 93%
CISA-KEV: Not listedEPSS PROB: 93%CVSS: 5.6Exploit: Elevated riskExposed: 262

A fix is available — apply it.

Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.

Live · internet exposure

262 internet-exposed hosts are running an affected version of CVE-2017-5753 right now.

across 52 countries (Thailand, United States, Viet Nam, France, China)top: esxi
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
5.6
EG Score
9.0(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
Severity90% × 45%
Exploitation94% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
93%
EPSS %ILE
100%
KEV
Not listed

Published

January 4, 2018

Last Modified

May 28, 2026

References (132)

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibwebkit2gtk-4.0-37 (2.18.5-0ubuntu0.17.04.1) @ zesty2026-05-28ubuntu
ubuntulinux-image-3.2.0-133-generic (3.2.0-133.179) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-31-generic (4.13.0-31.34~16.04.1) @ xenial2026-05-28ubuntu
ubuntunvidia-opencl-icd-384 (384.111-0ubuntu0.14.04.1) @ trusty2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-9023-euclid (4.4.0-9023.24) @ xenial2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-111-generic (4.4.0-111.134~14.04.1) @ trusty2026-05-28ubuntu
ubuntulinux-image-4.4.0-1017-kvm (4.4.0-1017.22) @ xenial2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-37-generic (4.13.0-37.42~16.04.1) @ xenial2026-05-28ubuntu
ubuntufirefox (57.0.4+build1-0ubuntu0.17.04.1) @ zesty2026-05-28ubuntu
ubuntulinux-image-generic (4.13.0.31.33) @ artful2026-05-28ubuntu
ubuntulinux-image-generic-lts-trusty (3.13.0.140.131) @ precise2026-05-28ubuntu
ubuntulinux-image-raspi2 (4.13.0.1015.13) @ artful2026-05-28ubuntu
ubuntulinux-image-extra-3.13.0-141-generic (3.13.0-141.190) @ trusty2026-05-28ubuntu
redhatkernel-alt-0:4.14.0-49.el7a2018-04-10redhat
redhatkernel-0:2.6.32-696.23.1.el62018-03-13redhat
redhatkernel-0:2.6.32-573.53.1.el62018-03-13redhat
redhatkernel-0:2.6.18-348.35.1.el52018-03-07redhat
redhatkernel-0:2.6.18-426.el52018-02-09redhat
redhatkernel-0:3.10.0-514.41.1.el72018-01-25redhat
redhatkernel-0:3.10.0-693.17.1.el72018-01-25redhat
redhatkernel-0:2.6.32-220.76.2.el62018-01-04redhat
redhatkernel-0:2.6.32-358.84.2.el62018-01-04redhat
redhatkernel-0:2.6.32-431.85.2.el62018-01-04redhat
redhatkernel-0:2.6.32-504.64.4.el62018-01-04redhat
redhatkernel-rt-0:3.10.0-693.11.1.rt56.639.el72018-01-04redhat
redhatkernel-rt-1:3.10.0-693.11.1.rt56.606.el6rt2018-01-04redhat
redhatkernel-0:3.10.0-327.62.4.el72018-01-03redhat

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

(25)

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 / 10× 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:30 UTCEG score recompute
  2. 2026-07-22 22:09 UTCEG score recompute
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-21 20:18 UTCOSV refresh
  6. 2026-07-15 16:54 UTCEPSS rescore
  7. 2026-07-04 15:56 UTCOSV refresh
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-28 14:04 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-16 03:13 UTCOSV refresh
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-05-31 22:28 UTCEPSS rescore
  15. 2026-05-31 22:28 UTCEPSS rescore
  16. 2026-05-29 13:41 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-28 12:54 UTCEG score recompute
  20. 2026-05-28 12:54 UTCVendor advisory
  21. 2026-05-27 13:38 UTCEPSS rescore
  22. 2026-05-27 13:38 UTCEPSS rescore
  23. 2026-05-23 02:35 UTCOSV refresh

Publicly available exploits

(5 references)

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

  • GitHub PoCixtal23/spectreScope
    First seen Jan 6, 2018

    The demo of the speculative execution attack Spectre (CVE-2017-5753, CVE-2017-5715).

    Open source ↗
  • GitHub PoC00052/spectre-attack-example
    First seen Jan 5, 2018

    2018年1月2日 (CVE-2017-5753 和 CVE-2017-5715) "幽灵" Spectre 漏洞利用

    Open source ↗
  • GitHub PoCEugnis/spectre-attack
    First seen Jan 4, 2018

    Example of using revealed "Spectre" exploit (CVE-2017-5753 and CVE-2017-5715)

    Open source ↗
  • GitHub PoCEdwardOwusuAdjei/Spectre-PoC
    First seen Jan 4, 2018

    Spectre (CVE-2017-5753) (CVE-2017-5715). Not By Me. Collected from Book.

    Open source ↗
  • Exploit-DBEDB-43427
    First seen Jan 3, 2018

    Multiple CPUs - 'Spectre' Information Disclosure

    Open source ↗

Past incidents using this CVE

(1)

This CVE was central to one or more publicly-documented breaches. Each card links to authoritative reporting at the time of the incident.

  • Spectre & Meltdown (CPU side-channel)Jan 2018

    Speculative-execution side-channel attacks against virtually every modern CPU (Intel, AMD, ARM). Required hardware-firmware updates and OS kernel changes across the industry.

    Source: ZDNet

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-5753?
CVE-2017-5753 is a critical vulnerability published on January 4, 2018. Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.
When was CVE-2017-5753 disclosed?
CVE-2017-5753 was first published in the National Vulnerability Database on January 4, 2018, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5753 actively exploited?
CVE-2017-5753 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2017-5753?
CVE-2017-5753 has a CVSS v3 base score of 5.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-5753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5753, 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-5753

Explore →

Is Your Infrastructure Affected by CVE-2017-5753?

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

Start Free Scan →Browse All CVEs