Patch today
Exploited in the wild
Confirmed attacks are already happening. Emergency change window.
No actively exploited vulnerabilities in this release.
Updated monthlyMicrosoft Patch Tuesday
Microsoft Patch Tuesday
December 2017
Microsoft's December 2017 Patch Tuesday fixes 36 vulnerabilities across Browser, Microsoft Office and Windows - 21 rated Critical. No active exploitation this month, so lead with the 21 Critical remote code execution fixes.
Released December 12, 2017, 10:00 PT40 KB articles to deploy
December 2017 Patch Tuesday at a glance
36
Microsoft CVEs
excl. Edge & Azure Linux
21
Critical
58% of the release
0
Actively exploited
none this month
0
Publicly disclosed
known before the patch
7.5
Highest CVSS
CVE-2017-11886
40
KB articles
what you actually deploy
Why this number differs from other roundups. Microsoft's December 2017 release document lists 39 entries. 2 are Azure Linux (Mariner) OS package updates and 1 are republished Chromium fixes for Edge - neither is a Microsoft product vulnerability. The 36 above is the real Patch Tuesday set. See the breakdown →
Priority order
Patch these first
Ranked by exploitation reality, not score alone. Nothing is under active attack this month, so the Critical remote-code-execution fixes lead.
Patch this week
Publicly disclosed
Details are already public. Working exploits typically follow within days.
Nothing was disclosed before the patch shipped.
Patch this cycle
Critical remote code execution
No known exploitation yet, but network-reachable and high impact.
CVE-2017-11886Scripting Engine Memory Corruption VulnerabilityCVE-2017-11890Scripting Engine Memory Corruption VulnerabilityCVE-2017-11894Scripting Engine Memory Corruption VulnerabilitySee all 21 Critical →The numbers
What’s in this release
Where the 39 entries actually come from
Most roundups quote a single number. These are three unrelated release streams.
36
2
1
36 Microsoft products2 Azure Linux (Mariner)1 Edge (Chromium)
Severity
Microsoft channel only · 36 CVEs
| Critical | 21 |
|---|---|
| Important | 13 |
| Moderate | 0 |
| Low | 0 |
| Unrated | 2 |
Impact type
What an attacker gains if it works
| Remote Code Execution | 25 |
|---|---|
| Information Disclosure | 6 |
| Other | 2 |
| Elevation of Privilege | 1 |
| Spoofing | 1 |
| Security Feature Bypass | 1 |
Most-affected components
Where this month’s fixes concentrate - filter by any of them in the table below
Microsoft Scripting Engine23Microsoft Office5Microsoft Exchange Server2Microsoft Malware Protection Engine2Microsoft Windows2Adobe Flash Player1Device Guard1
Every patch
Browse all 39 entries
Sorted by risk by default: exploited first, then publicly disclosed, then severity, then CVSS. Search by CVE, title, component or KB number.
| Title | Status | KB | |||||
|---|---|---|---|---|---|---|---|
| Critical | CVE-2017-11886 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11890 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11894 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11895 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +7 |
| Critical | CVE-2017-11901 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11903 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11907 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11912 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Critical | CVE-2017-11889 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +4 |
| Critical | CVE-2017-11893 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +3 |
| Critical | CVE-2017-11905 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +3 |
| Critical | CVE-2017-11908 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4054517 |
| Critical | CVE-2017-11909 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +3 |
| Critical | CVE-2017-11910 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +4 |
| Critical | CVE-2017-11911 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +3 |
| Critical | CVE-2017-11914 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +3 |
| Critical | CVE-2017-11918 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | 4053578 +4 |
| Important | CVE-2017-11913 | Scripting Engine Memory Corruption Vulnerability | RCE | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Important | CVE-2017-11919 | Scripting Engine Information Disclosure Vulnerability | Info Disc. | 7.5 | More likely | Microsoft Scripting Engine | 4052978 +7 |
| Important | CVE-2017-11887 | Internet Explorer Information Disclosure Vulnerability | Info Disc. | 4.3 | More likely | Microsoft Scripting Engine | 4052978 +7 |
| Important | CVE-2017-11906 | Internet Explorer Information Disclosure Vulnerability | Info Disc. | 4.3 | More likely | Microsoft Scripting Engine | 4052978 +8 |
| Important | CVE-2017-11916 | Scripting Engine Memory Corruption Vulnerability | RCE | 4.2 | More likely | Microsoft Scripting Engine | — |
| Important | CVE-2017-11935 | Microsoft Office Remote Code Execution Vulnerability | RCE | - | More likely | Microsoft Office | — |
| Unrated | ADV170021 | Microsoft Office Defense in Depth Update | Other | - | More likely | Microsoft Office | 4011575 +10 |
| Critical | CVE-2017-11937 | Microsoft Malware Protection Engine Remote Code Execution Vulnerability | RCE | - | — | Microsoft Malware Protection Engine | — |
Your move
What your IT team should do
The same five steps every month, in the order that reduces risk fastest.
Triage by exploitability, not CVSS
Nothing is under active attack this month, so rank by exploitability forecast and reachability rather than raw score. A Critical flaw on an internet-facing service outranks a higher-scoring one behind authentication.
Patch Management vs Vulnerability Management: What's the Difference? →Stage the rollout in rings
This release means 40 distinct update packages to deploy. Pilot on ring 0 within 24 hours and widen to production by day seven - never push the whole set everywhere at once.
What is Ring-Based Patch Deployment? A Guide to Progressive Rollouts →The Patch Management Lifecycle: 6 Stages from Discovery to Verification →Test the known-issue candidates
Check the Windows release health dashboard before promoting past ring 1, and have the rollback path written down before you need it. Kernel, networking and authentication fixes are the ones that historically break things.
12 Patch Management Best Practices for 2026 →Don't stop at the operating system
1 Chromium fixes for Edge shipped alongside this release on their own updater, and Adobe, SAP and Oracle release in the same week. OS-only patching leaves most of your real attack surface untouched.
What is Third-Party Patch Management and Why OS Patching Isn't Enough →Verify installed state, then evidence it
Confirm the patch is actually present on each endpoint rather than trusting that "deployment succeeded". Keep the resulting report - it is the artefact auditors ask for, and reconstructing it later is far more work than capturing it now.
Patch Management: The Complete Guide →Trinetri does steps two through five automatically - detecting the 40 KB articles across every endpoint, staging them in rings, verifying installed state and producing the compliance evidence. See patch management →
Archive
Previous Patch Tuesdays
Every month Microsoft has published back to January 2016, each with the same breakdown and the full CVE list.
October 2026October 13, 2026September 2026September 8, 2026August 2026August 11, 2026July 2026July 14, 2026June 2026June 9, 2026May 2026May 12, 2026April 2026April 14, 2026March 2026March 10, 2026February 2026February 10, 2026January 2026January 13, 2026December 2025December 9, 2025November 2025November 11, 2025October 2025October 14, 2025September 2025September 9, 2025August 2025August 12, 2025July 2025July 8, 2025June 2025June 10, 2025May 2025May 13, 2025April 2025April 8, 2025March 2025March 11, 2025February 2025February 11, 2025January 2025January 14, 2025December 2024December 10, 2024November 2024November 12, 2024
Older months104 releases, October 2024 – January 2016
2024
2023
2022
2021
2020
2019
2018
2017
Stop the sprawl. Eliminate the guesswork.
Ready to See Autonomous Endpoint Management in Action?
Experience how Trinetri transforms endpoint chaos into clarity. Try the 30 minute demo session, our experts will walk you through how AI-powered automation, real-time visibility, and unified control can secure your entire hybrid environment, without the overhead.
Patch Tuesday FAQ
Patch Tuesday falls on the second Tuesday of every month, with updates going live at 10:00 a.m. Pacific Time. Microsoft introduced the practice in October 2003, following the Blaster worm, to cut distribution costs and give administrators a predictable cadence instead of patches arriving at random. The 10:00 a.m. timing is deliberate: it leaves a full working week to remediate before the weekend. Internally Microsoft calls it the "B" release; optional "C" and "D" preview releases follow later in the month. The next Patch Tuesday is November 10, 2026.
Microsoft fixed 36 vulnerabilities in December 2017, across Browser, Microsoft Office, Windows and System Center. 21 are rated Critical, 0 were publicly disclosed before the patch shipped, and 0 were already being exploited. Note that Microsoft's release document lists 39 entries in total, but 2 of those are Azure Linux package updates and 1 are republished Chromium fixes for Edge, which is why other sources sometimes quote a much larger number.
Exploit Wednesday is the day after Patch Tuesday. Attackers compare the newly released patches against the previous version to locate the flaw each one fixes, then build working exploits from that difference - often within 24 to 48 hours. It is the reason the deployment window matters as much as the patch itself: every hour a Critical remote code execution fix sits undeployed is an hour of measurable exposure.
A workable target for most organisations: actively exploited vulnerabilities within 24 hours, publicly disclosed ones within 72 hours, remaining Critical fixes within seven days, and everything else within the month. CISA's Known Exploited Vulnerabilities catalogue sets binding deadlines for US federal agencies and is a reasonable benchmark for everyone else. Stage the rollout in rings rather than deploying everywhere at once, so a regression is caught on a pilot group instead of in production.
An out-of-band update is a patch released outside the monthly cycle because the risk will not wait for the next Patch Tuesday. Microsoft issues them for actively exploited flaws with no mitigation - most famously during the WannaCry outbreak in 2017, when it took the unusual step of patching versions of Windows that were already out of support.
Yes. Adobe aligned its releases with Patch Tuesday in November 2012, and both SAP's Security Patch Day and Oracle's quarterly Critical Patch Updates are coordinated to the same week. Part of the reason is defensive: staggered releases let attackers reverse-engineer one vendor's patch to find the same underlying flaw in another's still-unpatched product. For IT teams it means the second Tuesday is rarely just a Microsoft problem.
Edge is built on Chromium, so most of its security fixes originate with the Chromium project and are republished by Microsoft under their own CVE identifiers. They ship on Chromium's cadence rather than the Patch Tuesday cycle, and they are delivered by Edge's own updater rather than Windows Update. Counting the 1 Edge entries alongside Microsoft product fixes would inflate the headline number and imply work for your Windows Update rings that does not exist.