vciy

CVE-2015-6095

INDEX BUILT · 2026-10-18

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.

Kerberos in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2…

CVE-2015-60953 of 4 sources documented this
33

rank 33 = 16 + 12 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.04001  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.9, from NVD  ·  without this subject the record ranks 21

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 33

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 28

Someone else already set the date

CISA KEV remediation due date

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

Hindsight · the state

0.04001EPSSNOT IN KEVas of 2026-10-18
Severity4.9 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2025-03-30, 442 days at 0.04, as of 2026-06-15. 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

Which product do you run? 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

Choose your product above to watch it.

Set up a watchlist (free with an account: one stack of three products)

Record your call

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

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

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 · no authentication · low attack complexityreceipt
ImpactComplete integrity lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classCWE-255receipt
Published consequencesMITRE publishes no common consequences for this weakness.cwe-consequences@4.20

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 15 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.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2016-02-18.

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

Authority who says so

CVSS, NVD4.9 MEDIUMreceipt
Exploit probability0.04001 · top 10% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes24 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesMicrosoft windows server; Microsoft windowsreceipt
Published rangesmicrosoft windows 10 1511; microsoft windows server 2008 r2-sp1; 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.

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

$137,000 = $4.99M incident cost x 0.6870019236053861 exposure x 0.04001 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.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Kerberos in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 Gold and 1511 mishandles password changes, which allows physically proximate attackers to bypass authentication, and conduct decryption attacks against certain BitLocker configurations, by connecting to an unintended Key Distribution Center (KDC), aka "Windows Kerberos Security Feature Bypass." receipt

NVD's analysis a second authority

severity
4.9 AV:L/AC:L/Au:N/C:N/I:C/A:N
weakness
CWE-255
affected versions
microsoft windows 10 1511; microsoft windows server 2008 r2-sp1; microsoft windows server 2012 r2

check it yourself docs.microsoft.com securitytracker.com receipt

Dated events

2025-03-19EPSS moved 0.03 to 0.172025-03-30EPSS moved 0.17 to 0.04

Movement the material steps

4 Feb 20220.02829
7 Mar 20234.4e-4 · scoring model v2023.03.01
17 Mar 20250.03203 · scoring model v2025.03.14
19 Mar 20250.17261 · crossed 0.10
20 Mar 20250.03933 · crossed 0.10
27 Mar 20250.17261 · crossed 0.10
28 Mar 20250.03933 · crossed 0.10
29 Mar 20250.17261 · crossed 0.10
30 Mar 20250.03933 · crossed 0.10
15 Jun 20260.04001 · scoring model v2026.06.15

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

Show all 21 observations
4 Feb 20220.02829
7 Mar 20234.4e-4
8 Mar 20230.00044
17 Dec 20240.00066
17 Mar 20250.03203
19 Mar 20250.17261
20 Mar 20250.03933
27 Mar 20250.17261
28 Mar 20250.03933
29 Mar 20250.17261
30 Mar 20250.03933
28 Jun 20250.06476
1 Oct 20250.05975
27 Oct 20250.06476
28 Oct 20250.05975
20 Nov 20250.04574
27 Dec 20250.04966
28 Dec 20250.04574
4 Apr 20260.04541
31 May 20260.05236
15 Jun 20260.04001

21 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.04001Published2015-11-11Public PoC2016-02-18Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.03203 → 0.17261) and the record had been public for 10 years, 7 months when this index was last written.

Published 2015-11-11 receipt · Public PoC 2016-02-18 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.