SecurityNewsFor: IT and service desk · Business operations

US officials tie a week of outages to patching; flaw count tops 100,000

Officials blame rushed fixes, not an attack, for outages at Microsoft 365, banks and the FAA. IT leads have until 8 December to stage the next patches.

If you run IT, the week's outages now have an official explanation, and it is your monthly job: patching. Microsoft 365, the Federal Aviation Administration's air traffic network, Chase's online banking, Apple's services and the National Security Agency's internal network all failed between 12 and 17 November 2026. "We are not under systemic attack," Secretary of State Marco Rubio said on 18 November, adding that when companies patch vulnerabilities it can create a "short-term disruption in the way your system works", [Fortune reported](https://fortune.com/2026/11/18/nicole-perlroth-vulnpocalypse-outages-rubio-microsoft-faa-nsa/).

Director of National Intelligence Jay Clayton said the same a day earlier: "They're upgrading them, they're putting patches in place," at "a much larger scale" than before, [TechCrunch reported](https://techcrunch.com/2026/11/17/google-joins-the-tech-outage-trend-by-announcing-its-not-having-one/). Neither named a patch. The organisations' own accounts, as Fortune and [The Register](https://www.theregister.com/security/2026/11/17/daily-disruptive-outages-that-ground-planes-and-halt-work-welcome-to-the-new-normal/5310634) quote them: Microsoft, a bug introduced by a July update; the FAA, a contractor's network maintenance, with the root cause [still under investigation](https://fortune.com/2026/11/17/trump-administration-ai-outages-mullin-gary-marcus-banks-airlines/); Chase, "a software bug in on-premise hardware systems"; Apple, a faulty internal update; the NSA, "scheduled routine maintenance". None called it an attack.

Why there is more to patch

The security firm VulnCheck counted 100,222 publicly catalogued software flaws (CVEs, the numbered entries vendors patch against) for 2026 by 13 November, more than double all of 2025, [The Register reported](https://www.theregister.com/security/2026/11/13/this-years-bug-count-just-passed-100k/5309882). Microsoft's monthly update fixed 1,094 flaws on 10 November and 1,474 in October. "There's no denying the fact that vulnerability hunting with AI is driving a majority of what we're seeing," VulnCheck's Josh Bressers told the paper. VulnCheck also found the median time from a flaw's publication to its use in an attack fell from 120 days in 2025 to 80 days in the first half of 2026.

The catch: the catalogue does not record whether AI found a flaw, and IBM says its own count "does not establish a direct causal relationship", Fortune notes. About 1.4% of this year's flaws (1,363) have been used in attacks, by VulnCheck's count, so the list that needs patching this week has grown far less than the total.

The phishing that followed

On 13 November, the day after its outage began, Microsoft saw a high-volume phishing campaign posing as Microsoft 365 service-health notices, [its security blog said on 16 November](https://www.microsoft.com/en-us/security/blog/2026/11/16/high-volume-phishing-campaign-uses-microsoft-365-outage-lures-target-multiple-industry-sectors-2/). The emails carry the subject "Outage" followed by a random code, claim that messages held during the disruption will be deleted within 24 hours, and offer a "RESTORE MESSAGES" button that leads to a non-Microsoft site. Microsoft assesses the aim as password theft, has not confirmed any stolen credentials, and says Defender for Office 365 quarantines the messages.

The people and the cost

No source puts a cost on last week. The reference point Fortune gives is July 2024, when one faulty CrowdStrike update crashed more than 8.5 million Windows machines: the insurer Parametrix estimated $5.4 billion in direct losses for the Fortune 500, with cyber insurance covering 10% to 20%.

On the people doing the patching, [The Register quotes](https://www.theregister.com/security/2026/11/10/november-patch-tuesday-boasts-over-1000-bugs-one-already-under-attack/5308946) watchTowr's Jake Knott saying most security teams "haven't quite recovered from the last month of bumper-to-bumper critical vulnerabilities".

What to do before 8 December if you run IT

  • Put every update that installs itself behind a pilot group, and write down who undoes it and how. Do not respond by delaying everything: Dustin Childs of TrendAI's Zero Day Initiative told The Register to patch Exchange and domain controllers first, because attackers start work the minute a fix is published.
  • Send staff Microsoft's rule today: real service-health notices never send you to a non-Microsoft site to recover mail. Search mailboxes for the "Outage" subject pattern, and reset the password and sessions of anyone who clicked.
  • With finance and support leads, name how orders, payments and customer replies continue for a day without email or the bank portal, and ask your broker whether a faulty update with no attacker is covered.
Was this useful for your work?

Take this to work

Forward this

US officials attribute six days of outages at Microsoft 365, the FAA, Chase, Apple and the NSA (12 to 17 November 2026) to patching, not an attack, and VulnCheck counts over 100,000 published software flaws this year, double all of 2025, Fortune and The Register report. Our updates should go to a pilot group first, with a tested rollback, before Microsoft's 8 December release.

Questions to ask

  1. Which of our systems update automatically with no pilot group, and who can roll each one back, in how many minutes?
  2. Which vendors push updates into our environment without our approval, and what do their contracts pay if one takes us down?
  3. Does our cyber insurance pay for an outage caused by a faulty update with no attacker involved?
  4. How does each team take orders, pay suppliers and answer customers if email or the bank portal is down for a day?
  5. Did anyone here click an outage-themed "restore messages" email after 12 November, and have their sessions been revoked?

The arithmetic

people unable to work × working hours lost × loaded hourly cost, plus orders or payments delayed, minus what insurance or a service credit pays back

Parametrix's July 2024 figures: $5.4 billion in direct Fortune 500 losses with 10% to 20% insured leaves $4.3 billion to $4.9 billion uninsured ($5.4 billion × 80% to 90%). No source gives users affected, hours lost or a loss figure for the November 2026 outages; those inputs are yours.

Questions this article answers

Were the November 2026 outages a cyberattack?

US officials say no. Secretary of State Marco Rubio said on 18 November 2026 that "we are not under systemic attack", and Director of National Intelligence Jay Clayton said he saw no signs of a coordinated cyberattack, according to Fortune and TechCrunch. The FAA says it is still investigating its root cause.

What caused the outages at Microsoft 365, the FAA and Chase?

Each gave its own cause, as quoted by Fortune and The Register: Microsoft a bug introduced by a July update, the FAA a contractor's network maintenance, Chase a software bug in on-premise hardware systems. Officials tied the wave to patching at a larger scale than before and named no specific patch.

How many software vulnerabilities have been published in 2026?

VulnCheck counted 100,222 CVEs by about 16:00 UTC on 13 November 2026, more than double the 2025 total, The Register reported. About 1.4% of them (1,363) are in VulnCheck's catalogue of flaws known to be used in attacks.

Is the Microsoft 365 'restore messages' outage email real?

No. Microsoft said on 16 November 2026 that emails with the subject "Outage" plus a random code and a "RESTORE MESSAGES" button are a phishing campaign it first saw on 13 November. Real service-health notices do not send users to non-Microsoft sites; check the Microsoft 365 admin center instead.

Send this to someone who runs a teamLinkedInXBlueskyHNEmail