vciy

CVE-2023-36005

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.

Windows Telephony Server Elevation of Privilege Vulnerability

CVE-2023-360054 of 4 sources documented this
34

rank 34 = 6 + 20 + 0 + 8 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.23857  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.1, from NVD  ·  without this subject the record ranks 14

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 34

How much of the world it touches

NVD CPE configurations

10 products in the CPE ranges  ·  without this subject the record ranks 26

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.19Mover 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

$1.19M = $4.99M incident cost x 1 exposure x 0.23857 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.23857EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.0005 to 0.23857 across 25 observations. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-591, sensitive data storage in improperly locked memory. The index holds 77 prior instances of this class, 2 KEV-listed. taxonomy@v1

Full pattern panel

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

Sources disagree here.

Severity score
Microsoft7.5 HIGHreceipt
NVD8.1 HIGHreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Microsoft Windows 10 Version 1809? 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.

Reachnetwork-reachable · low privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-591 Sensitive Data Storage in Improperly Locked Memoryreceipt
Published consequencesCWE-591: Confidentiality: Read Application Data, Read Memory[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in10.0.17763.5206; 10.0.20348.2159; 10.0.22000.2652; 10.0.19041.3803; 10.0.22621.2861; 10.0.19045.3803; 10.0.22631.2861; 10.0.25398.584; 10.0.10240.20345…receipt
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, the CNA7.5 HIGHreceipt
CVSS, NVD8.1 HIGHreceipt
Exploit probability0.23857 · top 2% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes25 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1809; Microsoft Windows Server 2019; Microsoft Windows Server 2019 (Server Core installation); Microsoft Windows Server 2022; Microsoft Windows 11 version 21H2…receipt
Published rangesmicrosoft windows 10 1507 < 10.0.10240.20345; microsoft windows 10 1607 < 10.0.14393.6529; microsoft windows 10 1809 < 10.0.17763.5206; microsoft windows 10 21h2 < 10.0.19041.3803receipt
Show all 10 published ranges
microsoft windows 10 1507 < 10.0.10240.20345
microsoft windows 10 1607 < 10.0.14393.6529
microsoft windows 10 1809 < 10.0.17763.5206
microsoft windows 10 21h2 < 10.0.19041.3803
microsoft windows 10 22h2 < 10.0.19045.3803
microsoft windows 11 21h2 < 10.0.22000.2652
microsoft windows 11 22h2 < 10.0.22621.2861
microsoft windows 11 23h2 < 10.0.22631.2861
microsoft windows server 2008 r2
microsoft windows server 2012 r2
Fixed in10.0.17763.5206; 10.0.20348.2159; 10.0.22000.2652; 10.0.19041.3803; 10.0.22621.2861; 10.0.19045.3803; 10.0.22631.2861; 10.0.25398.584; 10.0.10240.20345…receipt

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.

Attack path

Network requestrequires low privilegesMicrosoft Windows Server 2019CWE-591 weaknessFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-591data compromise

What it is stated by the CNA

Windows Telephony Server Elevation of Privilege Vulnerability receipt

NVD's analysis a second authority

severity
8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-591
affected versions
microsoft windows 10 1507 < 10.0.10240.20345; microsoft windows 10 1607 < 10.0.14393.6529; microsoft windows 10 1809 < 10.0.17763.5206; and 7 more, listed in full below
also scored by
[email protected] 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

The CNA scored it 7.5 and NVD 8.1. Both are shown because both were published; we do not pick one.

check it yourself msrc.microsoft.com receipt

Dated events

2025-04-15EPSS moved 0.02 to 0.092026-06-15EPSS moved 0.09 to 0.24

Movement the material steps

13 Dec 20230.00050
17 Mar 20250.0043 · scoring model v2025.03.14
15 Jun 20260.23857 · crossed 0.10 · scoring model v2026.06.15

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

Show all 25 observations
13 Dec 20230.00050
19 Dec 20230.00138
14 Jan 20240.00111
24 Feb 20240.00157
20 Mar 20240.00111
16 May 20240.00128
20 Jul 20240.00156
7 Oct 20240.00130
18 Oct 20240.00161
31 Oct 20240.00113
11 Nov 20240.00123
17 Dec 20240.00163
18 Dec 20240.00198
13 Jan 20250.00204
20 Feb 20250.00203
17 Mar 20250.0043
19 Mar 20250.0081
25 Mar 20250.02415
29 Mar 20250.05194
30 Mar 20250.02415
15 Apr 20250.0877
2 May 20250.08837
18 Nov 20250.02415
21 Nov 20250.08837
15 Jun 20260.23857

25 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.23857Published2023-12-12Index as of2026-06-15

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.02415 → 0.08837) and the record had been public for 2 years, 6 months when this index was last written.

Published 2023-12-12 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-591, sensitive data storage in improperly locked memory. The index holds 77 prior instances of this class, 2 KEV-listed. [email protected]

CVE-2024-38106 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2024receipt
CVE-2023-28229 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2023receipt

77 records in this class held. The six above are ranked by exploit maturity, then recency.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2023-36005.

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.