Threats / Microsoft / CVE-2020-0638
CVE-2020-0638
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Microsoft Update Notification Manager vulnerability
Microsoft Update Notification Manager contains an unspecified privilege escalation vulnerability that has been exploited in the wild and leveraged in ransomware campaigns.
Verdict
Today item, not a backlog item.
A privilege escalation flaw in Update Notification Manager enables attackers to gain elevated system access. Active exploitation and ransomware deployment indicate material risk to Windows environments lacking timely patching.
CISA KEV Yes · 2022-05-234Ransomware use Flagged4EPSS 0.03042 (verify live)5CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-05-23), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.03042 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: Microsoft, Update Notification Manager. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 860 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I execute code with limited privileges on a target system running vulnerable Update Notification Manager.
Business
Initial compromise foothold established with user-level access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the privilege escalation vulnerability to elevate my access to system or administrator level.
Business
Attacker gains control sufficient to modify system configuration, disable security controls, and persist across reboots.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or additional malicious payloads with elevated privileges across the compromised environment.
Business
Widespread encryption of critical data, operational shutdown, and extortion demands materialize across the organization.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by microsoftCNA
Credited with finding itZhiniang Peng (@edwardzpeng) of Qihoo 360 Core Security and Jiadong Lufinder
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.