vciy

CVE-2017-5715 · Spectre

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an…

CVE-2017-57154 of 4 sources documented this
50

rank 50 = 26 + 14 + 0 + 10 + 0

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.74041  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.6, from NVD  ·  without this subject the record ranks 36

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 50

How much of the world it touches

NVD CPE configurations

20 products in the CPE ranges  ·  without this subject the record ranks 40

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 50

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.26Mover the next 30 days, if this record is yours
Movement-$82,100on 2026-01-18, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$2.26M = $4.99M incident cost x 0.6121449559255632 exposure x 0.74041 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.74041EPSSNOT IN KEVas of 2026-09-20
Severity5.6 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-06-15, 74 days at 0.74, as of 2026-08-28. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Intel Corporation Microprocessors with…? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-203 Observable Discrepancyreceipt
Published consequencesCWE-203: Confidentiality, Access Control: Read Application Data, Bypass Protection Mechanism; Confidentiality: Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 28 Aug 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 5 public repositories, 2018-01-09.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 5 public repositories2018-01-09receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD5.6 MEDIUMreceipt
Exploit probability0.74041 · top 0.54% of all CVEsreceipt
Blast breadth20 products across 1 vendorderived
Assigned byintelreceipt
Recorded changes95 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productIntel Corporation Microprocessors with Speculative Executionreceipt
Published rangesintel atom c c2308; intel atom c c2316; intel atom c c2338; intel atom c c2350receipt
Show all 20 published ranges
intel atom c c2308
intel atom c c2316
intel atom c c2338
intel atom c c2350
intel atom c c2358
intel atom c c2508
intel atom c c2516
intel atom c c2518
intel atom c c2530
intel atom c c2538
intel atom c c2550
intel atom c c2558
intel atom c c2718
intel atom c c2730
intel atom c c2738
intel atom c c2750
intel atom c c2758
intel atom c c3308
intel atom c c3338
intel atom c c3508

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Spectre is the common name for CVE-2017-5715. 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. cve-aliases@2026-08-27

NVD's analysis a second authority

severity
5.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
weakness
CWE-203
affected versions
intel atom c c2308; intel atom c c2316; intel atom c c2338; and 17 more, listed in full below
also scored by
5.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

check it yourself nvidia.custhelp.com usn.ubuntu.com lists.debian.org debian.org usn.ubuntu.com security.gentoo.org +14 morereceipt

Dated events

2022-02-04EPSS moved 0.46 to 0.872026-06-15EPSS moved 0.88 to 0.74

Movement the material steps

14 Apr 20210.45862000000000003
4 Feb 20220.87485 · crossed 0.50
12 Jun 20220.76928
7 Mar 20230.97581 · crossed 0.90 · scoring model v2023.03.01
17 Mar 20250.90181 · scoring model v2025.03.14
18 Jan 20260.88901 · crossed 0.90
15 Jun 20260.74041 · scoring model v2026.06.15
28 Aug 20260.74041
Show all 92 observations
14 Apr 20210.45862000000000003
16 Aug 20210.46126
4 Feb 20220.87485
13 Mar 20220.82652
12 Jun 20220.76928
1 Oct 20220.7494
7 Mar 20230.97581
8 May 20230.97546
8 Jul 20230.97485
15 Jul 20230.97549
14 Nov 20230.97548
15 Dec 20230.97515
17 Dec 20240.97469
17 Mar 20250.90181
19 Mar 20250.90097
21 Mar 20250.90658
28 Mar 20250.90558
3 Apr 20250.90821
9 Apr 20250.90481
15 Apr 20250.90443
18 Apr 20250.90558
20 Apr 20250.90658
1 May 20250.90583
3 May 20250.90982
5 May 20250.90583
11 May 20250.90982
12 May 20250.91016
14 May 20250.90658
15 May 20250.9096
16 May 20250.9052
21 May 20250.90558
27 May 20250.9096
3 Jun 20250.9089
15 Jun 20250.9096
17 Jun 20250.91259
18 Jun 20250.91049
22 Jun 20250.90982
16 Jul 20250.90948
17 Jul 20250.91016
18 Jul 20250.90621
22 Jul 20250.91016
23 Jul 20250.90658
30 Jul 20250.91049
5 Aug 20250.90982
16 Aug 20250.91016
19 Aug 20250.90658
28 Aug 20250.91049
1 Sep 20250.90982
17 Oct 20250.90948
19 Oct 20250.90545
20 Oct 20250.91016
23 Oct 20250.90925
24 Oct 20250.9096
6 Nov 20250.9089
18 Nov 20250.92142
21 Nov 20250.90558
24 Nov 20250.9096
1 Dec 20250.9089
18 Dec 20250.91644
24 Dec 20250.91588
18 Jan 20260.88901
20 Jan 20260.88266
21 Jan 20260.89008
25 Jan 20260.8906
7 Feb 20260.88954
18 Feb 20260.88386
21 Feb 20260.88444
2 Mar 20260.89521
6 Mar 20260.89423
9 Mar 20260.89094
10 Mar 20260.89423
13 Mar 20260.89094
14 Mar 20260.89423
16 Mar 20260.89094
20 Mar 20260.88954
21 Mar 20260.89008
22 Mar 20260.88386
25 Mar 20260.8854
27 Mar 20260.88597
7 Apr 20260.89198
9 Apr 20260.89094
21 Apr 20260.89198
23 Apr 20260.89147
26 Apr 20260.89042
28 Apr 20260.89198
11 May 20260.89094
22 May 20260.88424
23 May 20260.88597
5 Jun 20260.88482
15 Jun 20260.74041
24 Jul 20260.74207
28 Aug 20260.74041

92 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.74041Published2018-01-04Public PoC2018-01-09Index as of2026-08-28

The record had been public for 8 years, 7 months when this index was last written.

Published 2018-01-04 receipt · Public PoC 2018-01-09 receipt · Index as of 2026-08-28 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2017-5715.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.