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.0Trending — 3 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: EPSS in the top 5%, EPSS 50% or more, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2018-01-03 (Exploit-DB EDB-43427)EchelonGraph confidence 42%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.0 because EPSS predicted 94% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.6 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, NVD CVSS v3
Also known asEUVD-2017-14830 (ENISA EUVD)Source: ENISA EUVD
9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- 518 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%
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 94%CVSS: 5.6Exploit: Public PoCExposed services: 518
A fix is available — apply it.
Internet exposure · derived from Shodan data
518 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 68 countries (France, Thailand, United States, China, 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
- 63EG Risk 63/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity56% × 45%Impact severity (EG Severity): CVSS 5.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation94% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 94%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.6 MEDIUM): a likelihood of exploitation, not impact.
- EG Severity
- 5.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 94% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
January 4, 2018
Last Modified
May 28, 2026
Advisory Details (4)
Auto-updated Oct 14, 2026Patch available.
Web page
Packet Storm
http://packetstormsecurity.com/files/145645/Spectre-Information-Disclosure-Proof-Of-Concept.htmlWeb page
Security Bulletin: NVIDIA SHIELD TV Security Updates for CPU Speculative Side Channel Vulnerabilities | NVIDIA
http://nvidia.custhelp.com/app/answers/detail/a_id/4613Web page
Security Bulletin: NVIDIA Driver Security Updates for CPU Speculative Side Channel Vulnerabilities | NVIDIA
http://nvidia.custhelp.com/app/answers/detail/a_id/4611Web page
Security Notice: CPU Speculative Side Channel Vulnerabilities | NVIDIA
http://nvidia.custhelp.com/app/answers/detail/a_id/4609Vendor 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(28)
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:0091IMPORTANT2018-01-03
RHSA-2018:0091 — 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
Data Freshness Timeline
(refreshed 17× in last 7d / 54× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 94 are merged into the row they repeat.
- 2026-11-02 01:22 UTCEG score recompute
- 2026-11-02 01:22 UTCVendor advisory
- 2026-11-01 03:28 UTCEG score recompute
- 2026-11-01 03:28 UTCVendor advisory
- 2026-10-31 05:33 UTCEG score recompute
- 2026-10-31 05:33 UTCVendor advisory
- 2026-10-30 16:27 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-30 07:39 UTCEG score recompute
- 2026-10-30 07:39 UTCVendor advisory
- 2026-10-29 09:45 UTCEG score recompute
- 2026-10-29 09:45 UTCVendor advisory
- 2026-10-28 11:50 UTCEG score recompute
- 2026-10-28 11:50 UTCVendor advisory
- 2026-10-27 16:26 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-27 13:49 UTCEG score recompute
- 2026-10-27 13:49 UTCVendor advisory
- 2026-10-26 15:22 UTCVendor advisory
- 2026-10-25 16:36 UTCEG score recompute
- 2026-10-25 16:36 UTCVendor advisory
- 2026-10-25 16:27 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-24 18:41 UTCEG score recompute
- 2026-10-24 18:41 UTCVendor advisory
- 2026-10-23 20:47 UTCEG score recompute
- 2026-10-23 20:47 UTCVendor advisory
- 2026-10-22 22:46 UTCEG score recompute
Show 65 moreShow fewer
- 2026-10-22 22:46 UTCVendor advisory
- 2026-10-22 16:27 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-22 00:49 UTCEG score recompute
- 2026-10-22 00:49 UTCVendor advisory
- 2026-10-21 02:42 UTCEG score recompute
- 2026-10-21 02:42 UTCVendor advisory
- 2026-10-20 04:36 UTCEG score recompute
- 2026-10-20 04:36 UTCVendor advisory
- 2026-10-19 16:26 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-19 05:27 UTCEG score recompute
- 2026-10-19 05:27 UTCVendor advisory
- 2026-10-18 16:27 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-18 07:31 UTCEG score recompute
- 2026-10-18 07:31 UTCVendor advisory
- 2026-10-17 09:29 UTCEG score recompute
- 2026-10-17 09:29 UTCVendor advisory
- 2026-10-16 11:32 UTCEG score recompute
- 2026-10-16 11:32 UTCVendor advisory
- 2026-10-15 16:26 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-15 12:08 UTCEG score recompute
- 2026-10-15 12:08 UTCVendor advisory
- 2026-10-14 07:36 UTCEG score recompute
- 2026-10-14 07:36 UTCVendor advisory
- 2026-10-13 16:27 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-13 02:49 UTCVendor advisory
- 2026-10-12 20:27 UTCEG score recompute
- 2026-10-12 00:50 UTCEG score recompute
- 2026-10-11 13:41 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-10-07 23:41 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-09-30 09:34 UTCEG score recompute
- 2026-09-29 11:53 UTCOSV refresh
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-09-09 22:53 UTCOSV refresh
- 2026-09-07 15:56 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-09-06 13:43 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-09-05 15:23 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-09-01 03:31 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-08-26 14:41 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-08-23 01:06 UTCOSV refresh
- 2026-08-19 16:59 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-08-07 04:27 UTCOSV refresh
- 2026-08-06 13:42 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-07-30 16:24 UTCEPSS rescoreEPSS 93% · 99th percentile
- 2026-07-23 01:30 UTCEG score recompute
- 2026-07-22 22:09 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-07-21 20:18 UTCOSV refresh
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-07-04 15:56 UTCOSV refresh
- 2026-07-01 15:02 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-06-28 14:04 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-06-28 04:53 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-06-23 21:30 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-06-16 03:13 UTCOSV refresh
- 2026-06-15 17:45 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-31 22:28 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-29 13:41 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-28 13:42 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-28 12:54 UTCEG score recompute
- 2026-05-28 12:54 UTCVendor advisory
- 2026-05-27 13:38 UTCEPSS rescoreEPSS 94% · 99th percentile
- 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-severity vulnerability; its CVE record was 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 made public?
CVE-2017-5753 was made public on January 3, 2018: that is the date its CVE record's CNA, Intel Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 4, 2018. EchelonGraph's copy of the record carries a last-modified date of May 28, 2026; the record at its source may have been updated since.
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 + FIRST EPSS 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.