CVE-2017-5754

MEDIUMNVD 5.65.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.6 under NVD CVSS v3. EPSS exploit probability: 84.2%, top 0% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
5.6
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 84%
CISA-KEV: Not listedEPSS: 84%CVSS: 5.6Exploit: NoneExposed: 0

A fix is available — apply it.

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

CVSS v3
5.6
EG Score
5.6(medium)
EPSS
99.7%
KEV
Not listed

Published

January 4, 2018

Last Modified

May 28, 2026

References (132)

Vendor Advisories for CVE-2017-5754(2)

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

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-generic (3.2.0.132.146) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-3.13.0-142-generic (3.13.0-142.191) @ trusty2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-31-generic (4.13.0-31.34~16.04.1) @ xenial2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-26-generic (4.13.0-26.29~16.04.2) @ xenial2026-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-extra-4.4.0-108-generic (4.4.0-108.131~14.04.1) @ trusty2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-9021-euclid (4.4.0-9021.22) @ xenial2026-05-28ubuntu
ubuntulinux-image-extra-3.13.0-139-generic (3.13.0-139.188) @ trusty2026-05-28ubuntu
ubuntulinux-image-generic-lts-trusty (3.13.0.139.129) @ precise2026-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-raspi2 (4.13.0.1015.13) @ artful2026-05-28ubuntu
ubuntulinux-image-lowlatency (4.13.0.25.26) @ artful2026-05-28ubuntu
redhatkernel-alt-0:4.14.0-49.2.2.el7a2018-05-14redhat
redhatkernel-0:2.6.32-696.28.1.el62018-05-08redhat
redhatkernel-0:2.6.32-573.55.2.el62018-05-08redhat
redhatkernel-0:3.10.0-514.48.1.el72018-04-17redhat
redhatkernel-0:3.10.0-862.el72018-04-10redhat
redhatkernel-0:2.6.18-348.35.1.el52018-03-07redhat
redhatkernel-0:2.6.18-426.el52018-02-09redhat
redhatkernel-0:2.6.32-504.64.4.el62018-01-04redhat
redhatkernel-0:2.6.32-431.85.2.el62018-01-04redhat
redhatkernel-rt-0:3.10.0-693.11.1.rt56.639.el72018-01-04redhat
redhatkernel-0:2.6.32-358.84.2.el62018-01-04redhat
redhatkernel-0:2.6.32-220.76.2.el62018-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.

Additional Vendor Advisories

(23)

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 7× 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-22 22:09 UTCEG score recompute▼ 3.40
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-21 19:48 UTCOSV refresh
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-18 10:00 UTCEPSS rescore
  8. 2026-07-15 16:54 UTCEPSS rescore
  9. 2026-07-09 19:06 UTCEPSS rescore
  10. 2026-07-04 15:26 UTCOSV refresh
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-06-27 03:06 UTCEPSS rescore
  14. 2026-06-27 03:05 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-16 03:13 UTCOSV refresh
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-13 22:57 UTCEPSS rescore
  22. 2026-06-10 22:15 UTCEPSS rescore
  23. 2026-06-10 13:19 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-08 14:14 UTCEPSS rescore
Show 17 more
  1. 2026-06-05 22:44 UTCEPSS rescore
  2. 2026-06-04 13:10 UTCEPSS rescore
  3. 2026-06-02 20:11 UTCEPSS rescore
  4. 2026-06-02 20:11 UTCEPSS rescore
  5. 2026-05-31 22:28 UTCEPSS rescore
  6. 2026-05-31 22:28 UTCEPSS rescore
  7. 2026-05-31 00:14 UTCEPSS rescore
  8. 2026-05-31 00:14 UTCEPSS rescore
  9. 2026-05-28 13:42 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-28 12:54 UTCEG score recompute
  12. 2026-05-28 12:54 UTCVendor advisory
  13. 2026-05-26 13:42 UTCEPSS rescore
  14. 2026-05-26 13:42 UTCEPSS rescore
  15. 2026-05-26 07:17 UTCEPSS rescore
  16. 2026-05-26 07:17 UTCEPSS rescore
  17. 2026-05-23 02:35 UTCOSV refresh

Publicly available exploits

(3 references)

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

  • GitHub PoCViralmaniar/In-Spectre-Meltdown
    First seen Jan 5, 2018

    This tool allows to check speculative execution side-channel attacks that affect many modern processors and operating systems designs. CVE-2017-5754 (Meltdown) and CVE-2017-5715 (Spectre) allows unprivileged processes to steal secrets from privileged processes. These attacks present 3 different ways of attacking data protection measures on CPUs enabling attackers to read data they shouldn't be able to. This tool is originally based on Microsoft: https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in

    Open source ↗
  • GitHub PoCionescu007/SpecuCheck
    First seen Jan 4, 2018

    SpecuCheck is a Windows utility for checking the state of the software mitigations and hardware against CVE-2017-5754 (Meltdown), CVE-2017-5715 (Spectre v2), CVE-2018-3260 (Foreshadow), and CVE-2018-3639 (Spectre v4)

    Open source ↗
  • GitHub PoCraphaelsc/Am-I-affected-by-Meltdown
    First seen Jan 4, 2018

    Meltdown Exploit / Proof-of-concept / checks whether system is affected by Variant 3: rogue data cache load (CVE-2017-5754), a.k.a MELTDOWN.

    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-5754?
CVE-2017-5754 is a medium vulnerability published on January 4, 2018. Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.
When was CVE-2017-5754 disclosed?
CVE-2017-5754 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-5754 actively exploited?
CVE-2017-5754 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-5754?
CVE-2017-5754 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2017-5754?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5754, 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-5754

Explore →

Is Your Infrastructure Affected by CVE-2017-5754?

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

Start Free Scan →Browse All CVEs