RU

AI-Powered Vulnerability Hunting Sped Up Patching — and Triggered Outages at Microsoft and Chase

Published: 2026-11-18 · Author: AI Release · @ai_releaseorg
AI-Powered Vulnerability Hunting Sped Up Patching — and Triggered Outages at Microsoft and Chase

⚡ The gist

🔍 What happened

Over the past five days, outages have hit Microsoft 365, JPMorgan Chase, and Charles Schwab. Separately, flights at every US airport were briefly halted — Transportation Secretary Sean Duffy blamed aging air traffic control infrastructure. Business Insider reports, citing CNBC.

The mechanism officials and executives are discussing: AI scanners are uncovering holes in other people's code — and their own — that had gone unnoticed for years. Then comes the "mad rush" to patch, as Senate Intelligence Committee vice chair Mark Warner put it. Patches ship in batches, nobody has time to test every downstream effect, and an update breaks something that used to work. Kevin Mandia of Armadin put it this way: "sometimes you do that at a speed where you couldn't test all the potential outcomes of the update." The trigger, they say, was last month: AI found major holes in a programming language that powers up to 70% of websites. After that, per the report, came a crypto heist, hacked refrigerators, and attempts to literally boil blood.

🧠 Our take

The logic here is inverted from the usual narrative: AI isn't breaking systems — it's pushing people to fix them too fast. Our read: this is the first large-scale side effect of "AI security auditing." Scanners made vulnerability discovery cheap, the fix backlog ballooned, but release and testing processes stayed exactly the same. The bottleneck has moved from finding holes to shipping patches.

What does that mean for the rest of us? Bank and cloud outages stop being emergencies and become the cost of doing hygiene. For the market, it means demand for staged rollouts, canary releases, and proper postmortems — not yet another scanner. In our experience, companies that mandate stop-tests between patch waves lose days of speed but don't lose weekends.

Who wins: scanner vendors and safe-deployment platform makers, plus cyber insurers — they finally have something to price. Who loses: SRE teams and on-call engineers, who absorb every wave, and the reputation of the cloud itself. Mandia is betting on the long game, calling this the "first inning." We'd bet differently: the payoff will come, but someone else's downtime will pay for it.

⚠️ What we don't know

There are plenty of weak spots. Neither Microsoft, nor Chase, nor Schwab has publicly named the patch that broke their service — the AI-patching link rests on comments from Warner and Mandia, not on technical postmortems. The programming language with "holes affecting 70% of sites" is never named, no patch counts are given, and the share of bad updates is unknown. The airport story, meanwhile, got an entirely different official explanation. The Business Insider piece is partially paywalled, so readers will have to dig for some details in the companies' own postmortems.

💬 Worth debating

  • Patch everything at once, or roll out in waves with a testing delay — which mode would you pick for a bank that can't afford a full day of downtime?
  • If an AI scanner finds a critical hole but the patch takes down production, who's on the hook: the scanner's developer, the patch author, or whoever hit "deploy"?
  • Should regulators require public postmortems for outages the way they do for data breaches — or would that hand attackers a map of the infrastructure?

Disclaimer: Not officially confirmed: the link between the Microsoft 365, JPMorgan Chase, and Charles Schwab outages and accelerated AI patching rests solely on comments from Senator Mark Warner and Armadin CEO Kevin Mandia — none of the companies has named a specific update or patch that broke anything.

Forecast: Within the quarter, Microsoft, Chase, or Schwab will publish a postmortem naming a specific update — not "configuration" or "human error" — as the cause of an outage. If that doesn't happen, the AI-patching theory will remain a tidy hypothesis without a single confirmed case.

🤖 AI summary
  • Date: 2026-11-18
  • Source: www.businessinsider.com
  • Tags: cybersecurity, патчи, outages, AI, Microsoft, AI, MachineLearning, vulnerabilities
  • Key facts:
    • Over five days, outages hit Microsoft 365, JPMorgan Chase, and Charles Schwab — and US flights were briefly grounded at every airport in the country.
    • Senator Mark Warner and Armadin CEO Kevin Mandia explain the wave this way: AI is finding vulnerabilities faster than companies can properly vet the patches.
    • No single outage has been officially tied to a specific update — the theory is still being floated in general terms.
    • Over the past five days, outages have hit Microsoft 365, JPMorgan Chase, and Charles Schwab.
    • Separately, flights at every US airport were briefly halted — Transportation Secretary Sean Duffy blamed aging air traffic control infrastructure.
    • Business Insider reports , citing CNBC.
    • The mechanism officials and executives are discussing: AI scanners are uncovering holes in other people's code — and their own — that had gone unnoticed for years.
    • Then comes the "mad rush" to patch, as Senate Intelligence Committee vice chair Mark Warner put it.
#кибербезопасность#патчи#сбои#ИИ#Microsoft#AI#MachineLearning#уязвимости
← PreviousCiti, JPMorgan and PNC: When an AI Agent Gets Hacked, the Customer PaysNext →Boston Dynamics' Atlas Is Heading to GlobalFoundries' Fabs in Early 2027

Source: www.businessinsider.com · post in Telegram