vciy

CVE-2018-3640

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 that perform speculative reads of system registers may allow unauthorized disclosure…

CVE-2018-36404 of 4 sources documented this
26

rank 26 = 2 + 14 + 0 + 10 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.07556  ·  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 12

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 26

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$231,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$231,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.07556 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.07556EPSSNOT IN KEVas of 2026-09-20
Severity5.6 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2021-04-14, 1971 days at 0.08, as of 2026-09-06. 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? 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.0 · 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 6 Sep 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: Nothing observed in held sources.

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

Authority who says so

CVSS, NVD5.6 MEDIUMreceipt
Exploit probability0.07556 · top 6% of all CVEsreceipt
Blast breadth20 products across 1 vendorderived
Assigned byintelreceipt
Recorded changes35 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productIntel Corporationreceipt
Published rangesintel atom c c2308; intel atom c c3308; intel atom c c3338; intel atom c c3508receipt
Show all 20 published ranges
intel atom c c2308
intel atom c c3308
intel atom c c3338
intel atom c c3508
intel atom c c3538
intel atom c c3558
intel atom c c3708
intel atom c c3750
intel atom c c3758
intel atom c c3808
intel atom c c3830
intel atom c c3850
intel atom c c3858
intel atom c c3950
intel atom c c3955
intel atom c c3958
intel atom e e3805
intel atom e e3815
intel atom e e3825
intel atom e e3826

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

Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis, aka Rogue System Register Read (RSRE), Variant 3a. receipt

NVD's analysis a second authority

severity
5.6 CVSS:3.0/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 c3308; intel atom c c3338; and 17 more, listed in full below

check it yourself cert-portal.siemens.com support.lenovo.com us-cert.gov securitytracker.com securitytracker.com psirt.global.sonicwall.com +14 morereceipt

Movement the material steps

14 Apr 20210.04373
7 Mar 20230.00217 · scoring model v2023.03.01
17 Mar 20250.01108 · scoring model v2025.03.14
15 Jun 20260.07556 · scoring model v2026.06.15
6 Sep 20260.07556

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 35 observations
14 Apr 20210.04373
4 Feb 20220.01864
16 Feb 20230.01916
7 Mar 20230.00217
12 Mar 20230.00324
8 May 20230.00264
30 Mar 20240.00258
17 Dec 20240.00615
17 Mar 20250.01108
19 Mar 20250.01271
29 Mar 20250.02856
30 Mar 20250.01271
15 May 20250.01123
27 May 20250.01271
19 Jul 20250.01182
11 Oct 20250.01021
17 Oct 20250.00777
19 Oct 20250.00902
24 Oct 20250.00796
6 Nov 20250.00902
18 Nov 20250.00141
21 Nov 20250.00902
25 Jan 20260.00895
18 Feb 20260.0079
19 Feb 20260.00895
14 Mar 20260.00902
21 Apr 20260.01343
23 Apr 20260.01556
28 Apr 20260.01375
11 May 20260.01556
15 Jun 20260.07556
23 Aug 20260.0828
30 Aug 20260.07556
5 Sep 20260.0828
6 Sep 20260.07556

35 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.07556Published2018-05-22Index as of2026-09-06

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.00141 → 0.00902) and the record had been public for 8 years, 3 months when this index was last written.

Published 2018-05-22 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Its defect family

intel corporation multiple

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

Nothing we hold separates this record from the others in its defect family. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2018-3640.

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.