vciy

CVE-2015-1637

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.

Schannel (aka Secure Channel) in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8…

CVE-2015-16373 of 4 sources documented this
18

rank 18 = 3 + 11 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.13151  ·  without this subject the record ranks 15

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.3, from NVD  ·  without this subject the record ranks 7

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 18

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 14

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$188,000over the next 30 days, if this record is yours
Movement-$79,300on 2025-06-12, the last material move, 1 year before this reading
Basisassumeda published average, not your estate

$188,000 = $4.99M incident cost x 0.28625080150224425 exposure x 0.13151 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.13151EPSSNOT IN KEVas of 2026-09-20
Severity4.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementfallenreceipt
FALLING10Fallen from 0.29571 to 0.13151 across 18 observations. 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

Check a version against this record

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.

Reachnetwork-reachable · no authenticationreceipt
ImpactPartial integrity lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classCWE-310receipt
Published consequencesMITRE publishes no common consequences for this weakness.[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 20 Jun 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, NVD4.3 MEDIUMreceipt
Exploit probability0.13151 · top 4% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesMicrosoft windows serverreceipt
Published rangesmicrosoft windows server 2008 r2; microsoft windows server 2012 r2receipt

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

Schannel (aka Secure Channel) in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 does not properly restrict TLS state transitions, which makes it easier for remote attackers to conduct cipher-downgrade attacks to EXPORT_RSA ciphers via crafted TLS traffic, related to the "FREAK" issue, a different vulnerability than CVE-2015-0204 and CVE-2015-1067. receipt

NVD's analysis a second authority

severity
4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
weakness
CWE-310
affected versions
microsoft windows server 2008 r2; microsoft windows server 2012 r2

check it yourself technet.microsoft.com securitytracker.com securityfocus.com freakattack.com docs.microsoft.com web.archive.org receipt

Dated events

2023-03-07EPSS moved 0.33 to 0.962026-06-15EPSS moved 0.44 to 0.13

Movement the material steps

4 Feb 20220.29571
7 Mar 20230.96341 · crossed 0.50 and 0.90 · scoring model v2023.03.01
17 Dec 20240.78373 · crossed 0.90
17 Mar 20250.53481 · scoring model v2025.03.14
29 Mar 20250.48615 · crossed 0.50
30 Mar 20250.53481 · crossed 0.50
12 Jun 20250.47926 · crossed 0.50
15 Jun 20260.13311 · scoring model v2026.06.15
20 Jun 20260.13151
Show all 18 observations
4 Feb 20220.29571
25 Jul 20220.31152
5 Oct 20220.33187
7 Mar 20230.96341
16 Oct 20240.96354
17 Dec 20240.78373
17 Mar 20250.53481
29 Mar 20250.48615
30 Mar 20250.53481
12 Jun 20250.47926
1 Oct 20250.43723
27 Oct 20250.47926
28 Oct 20250.43723
27 Dec 20250.47926
28 Dec 20250.43723
15 Jun 20260.13311
17 Jun 20260.1322
20 Jun 20260.13151

18 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.13151Published2015-03-06Index as of2026-06-20

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

Published 2015-03-06 receipt · Index as of 2026-06-20 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2015-1637.

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.