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.
CVE-2017-5753
CRITICALNVD 5.69.0▲Elevated
EchelonGraph scoreHIGH confidence
Score elevated to 9.0 because EPSS predicts 94% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 5.6 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
- 697 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- High exploitation likelihood — EPSS 94%
CISA-KEV: Not listedEPSS PROB: 94%CVSS: 5.6Exploit: Elevated riskExposed services: 697
A fix is available — apply it.
Internet exposure · derived from Shodan data
697 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2017-5753, in our KEV-Exposure radar’s Shodan-derived sample.
across 71 countries (France, China, Thailand, United States, Viet Nam)top: esxi
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 5.6
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 78EG Risk 78/100CISA SSVC
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 computedSeverity90% × 45%Exploitation94% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 94%
- EPSS %ILE
- 99th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
January 4, 2018
Last Modified
May 28, 2026
References (132)
- secure@intelhttp://lists.opensuse.org/opensuse-security-announce/2018-01/msg00006.html
- secure@intelhttp://lists.opensuse.org/opensuse-security-announce/2018-01/msg00007.html
- secure@intelhttp://lists.opensuse.org/opensuse-security-announce/2018-01/msg00008.html
- secure@intelhttp://lists.opensuse.org/opensuse-security-announce/2018-01/msg00014.html
- secure@intelhttp://lists.opensuse.org/opensuse-security-announce/2018-01/msg00016.html
- secure@intelhttp://nvidia.custhelp.com/app/answers/detail/a_id/4609
- secure@intelhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611
- secure@intelhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613
- secure@intelhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614
- secure@intelhttp://packetstormsecurity.com/files/145645/Spectre-Information-Disclosure-Proof-Of-Concept.html
- secure@intelhttp://www.arubanetworks.com/assets/alert/ARUBA-PSA-2018-001.txt
- secure@intelhttp://www.arubanetworks.com/assets/alert/ARUBA-PSA-2019-003.txt
- secure@intelhttp://www.kb.cert.org/vuls/id/584653
- secure@intelhttp://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- secure@intelhttp://www.securityfocus.com/bid/102371
Vendor Advisories for CVE-2017-5753(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(27)
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.
Affected Packages
(26 across 21 ecosystems)
Debian:11(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions) |
| — |
Debian:12(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions) |
| — |
Debian:13(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions) |
| — |
Debian:14(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions) |
| — |
Debian:8(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (56 versions) |
| — |
| linux-4.9 | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-ucode | — |
| — |
Alpine:v3.5(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| xen | — |
| — |
Alpine:v3.6(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| xen | — |
| — |
Alpine:v3.7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| xen | — |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 4.9.30-2 ... 4.9.88-1~bpo8+1 (25 versions) |
| — |
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.
- Red HatRHSA-2018:0010IMPORTANT2018-01-03
RHSA-2018:0010 — Important
- Red HatRHSA-2018:0016IMPORTANT2018-01-03
RHSA-2018:0016 — Important
- Red HatRHSA-2018:0017IMPORTANT2018-01-03
RHSA-2018:0017 — Important
- Red HatRHSA-2018:0018IMPORTANT2018-01-03
RHSA-2018:0018 — Important
- Red HatRHSA-2018:0020IMPORTANT2018-01-03
RHSA-2018:0020 — Important
- Red HatRHSA-2018:0021IMPORTANT2018-01-03
RHSA-2018:0021 — Important
- Red HatRHSA-2018:0022IMPORTANT2018-01-03
RHSA-2018:0022 — Important
- Red HatRHSA-2018:0151IMPORTANT2018-01-03
RHSA-2018:0151 — Important
- Red HatRHSA-2018:0182IMPORTANT2018-01-03
RHSA-2018:0182 — Important
- Red HatRHSA-2018:0292IMPORTANT2018-01-03
RHSA-2018:0292 — Important
- Red HatRHSA-2018:0464IMPORTANT2018-01-03
RHSA-2018:0464 — Important
- Red HatRHSA-2018:0496IMPORTANT2018-01-03
RHSA-2018:0496 — Important
- Red HatRHSA-2018:0512IMPORTANT2018-01-03
RHSA-2018:0512 — Important
- Red HatRHSA-2018:0654IMPORTANT2018-01-03
RHSA-2018:0654 — Important
- UbuntuUSN-3516-1HIGH
Firefox vulnerabilities
- UbuntuUSN-3521-1HIGH
NVIDIA graphics drivers vulnerability
- UbuntuUSN-3530-1HIGH
WebKitGTK+ vulnerabilities
- UbuntuUSN-3540-1HIGH
Linux kernel vulnerabilities
- UbuntuUSN-3540-2HIGH
Linux kernel (Xenial HWE) vulnerabilities
- UbuntuUSN-3541-1HIGH
Linux kernel vulnerabilities
- UbuntuUSN-3541-2HIGH
Linux kernel (HWE) vulnerabilities
- UbuntuUSN-3542-1HIGH
Linux kernel vulnerabilities
- UbuntuUSN-3542-2HIGH
Linux kernel (Trusty HWE) vulnerabilities
- UbuntuUSN-3549-1HIGH
Linux kernel (KVM) vulnerabilities
- UbuntuUSN-3580-1HIGH
Linux kernel vulnerabilities
Data Freshness Timeline
(refreshed 1× in last 7d / 5× 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.
- 2026-10-07 23:41 UTCEPSS rescore
- 2026-09-30 09:34 UTCEG score recompute
- 2026-09-29 11:53 UTCOSV refresh
- 2026-09-24 13:59 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-09 22:53 UTCOSV refresh
- 2026-09-07 15:56 UTCEPSS rescore
- 2026-09-06 13:43 UTCEPSS rescore
- 2026-09-05 15:23 UTCEPSS rescore
- 2026-09-01 03:31 UTCEPSS rescore
- 2026-08-30 19:13 UTCEPSS rescore
- 2026-08-26 14:41 UTCEPSS rescore
- 2026-08-23 01:06 UTCOSV refresh
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-07 04:27 UTCOSV refresh
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-23 01:30 UTCEG score recompute
- 2026-07-22 22:09 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 20:18 UTCOSV refresh
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-04 15:56 UTCOSV refresh
Show 16 moreShow fewer
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-16 03:13 UTCOSV refresh
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-29 13:41 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 12:54 UTCEG score recompute
- 2026-05-28 12:54 UTCVendor advisory
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-23 02:35 UTCOSV refresh
Publicly available exploits
(5 references)Public exploit code is referenced for this CVE (1 Exploit-DB entry, 4 GitHub PoCs). Defenders should treat patch urgency accordingly.
- GitHub PoCixtal23/spectreScopePublished Jan 6, 2018
The demo of the speculative execution attack Spectre (CVE-2017-5753, CVE-2017-5715).
Open source ↗ - GitHub PoC00052/spectre-attack-examplePublished Jan 5, 2018
2018年1月2日 (CVE-2017-5753 和 CVE-2017-5715) "幽灵" Spectre 漏洞利用
Open source ↗ - GitHub PoCEdwardOwusuAdjei/Spectre-PoCPublished Jan 4, 2018
Spectre (CVE-2017-5753) (CVE-2017-5715). Not By Me. Collected from Book.
Open source ↗ - GitHub PoCEugnis/spectre-attackPublished Jan 4, 2018
Example of using revealed "Spectre" exploit (CVE-2017-5753 and CVE-2017-5715)
Open source ↗ - Exploit-DBEDB-43427Published 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 product + same vendor + same CWE)
Same product
10 shownAlpine:v3.13:intel-ucode
Same vendor
10 shownredhat:RHSA-2018:0016 · redhat:RHSA-2018:0010 · redhat:RHSA-2018:0151
Same CWE
10 shownCWE-203
- CVE-2017-5715NVD 5.6EG 8.3EPSS p99HIGH
- CVE-2017-12373EG 5.9EPSS p96MEDIUM
- CVE-2017-17427EG 5.9EPSS p97MEDIUM
- CVE-2017-13099EG 5.9EPSS p98MEDIUM
- CVE-2017-13098EG 5.9EPSS p98MEDIUM
- CVE-2017-1000385EG 5.9EPSS p98MEDIUM
- CVE-2018-0134EG 5.3MEDIUM
- CVE-2017-6168EG 7.4EPSS p97HIGH
- CVE-2018-1000119EG 5.9MEDIUM
- CVE-2017-5107EG 5.3MEDIUM
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 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 94% probability of exploitation in the next 30 days (99th percentile of EPSS-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 (CRITICAL).
How do I remediate CVE-2017-5753?
A fix for CVE-2017-5753 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-5753 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5753
Is Your Infrastructure Affected by CVE-2017-5753?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.