Satya Nadella says critical infrastructure firmware and cooling systems are unpatchable
Microsoft’s CEO has warned that vast swaths of critical infrastructure rely on firmware and cooling systems that cannot be patched, leaving them vulnerable to AI-powered cyberattacks. The admission underscores how the rush to connect legacy systems to the internet has created security blind spots that neither software updates nor traditional defenses can fix.
- Satya Nadella said firmware, chillers, and HVAC systems across critical infrastructure are “unpatchable” and connected to the internet.
- AI has accelerated exploitation of vulnerabilities faster than patches can be safely tested and deployed to production systems.
- Microsoft itself experienced a global Outlook outage caused by a latent bug, forcing the company to rethink its patching velocity and stability tradeoffs.
- November 18 Date of Nadella’s remarks at the New York Times DealBook Summit in 2026
- Transportation Critical sector Nadella cited as having discoverable but unpatchable firmware vulnerabilities
During an appearance at the New York Times’ DealBook Summit on Wednesday (November 18), Microsoft CEO Satya Nadella highlighted a structural vulnerability in America’s critical infrastructure: software systems powering everyday hardware and transportation lack the ability to receive security patches, even as they sit exposed on the internet. TechCrunch reported on his comments, which came amid concerns about AI-enabled cyberattacks and a string of recent outages affecting major technology platforms.
Remember, there is a lot of stuff in our critical infrastructure that’s unpatchable. I mean, think about all the firmware and the chillers and the HVAC systems everywhere else. So all of that, by the way, they’re on the internet.
Satya Nadella, CEO, Microsoft
Firmware and cooling systems create unfixable security gaps
Chillers are critical components of commercial HVAC systems used in data centers, hospitals, schools, and manufacturing plants to cool large buildings by circulating temperature-controlled liquid through piping systems. These devices, along with firmware in transportation networks and other legacy industrial systems, often run on code that cannot be updated remotely or was designed before internet connectivity became standard.
Nadella’s warning reflects a broader problem created by what he called the “smartification” of the economy: devices originally designed as disconnected hardware were retrofitted with network connectivity without adequate security architecture. The firmware governing these systems frequently lacks the ability to receive patches, turning them into permanent vulnerability vectors in an era when attackers increasingly use artificial intelligence to discover and exploit weaknesses at scale.
Patches now deploy faster than they can be safely tested
The acceleration of cyberattack sophistication has forced companies into a dangerous speed-versus-stability tradeoff. Nadella acknowledged that artificial intelligence has made it easier for attackers to find vulnerabilities, compressing the window between discovery and exploitation in the wild. When a vulnerability is disclosed or discovered, it can be attacked within hours rather than weeks.
“The patch needs to go instantly from being available to being patched in production, because it’s being exploited in the wild, right?” Nadella said. “So that’s going to create instability.” Companies historically had time to test patches, understand their operational impact, and roll them out carefully; that luxury no longer exists when threats move as fast as AI can generate them. The result is that speed of patching now outpaces the testing that would once have prevented unintended consequences.
Microsoft’s Outlook outage illustrates the cost of velocity
Microsoft itself confronted this reality when a global Outlook outage disrupted email service across the platform.
Nadella attributed the incident to a “latent bug” that created a “perfect storm” of conditions. He stated that Microsoft would extract learnings from the incident at both the architectural and operational levels, but his comments made clear that the company’s own patch velocity and production deployment practices contributed to the incident. The acknowledgment signals that even the world’s largest software company struggles with the new calculus of security: move fast and risk stability, or move carefully and accept longer exposure to known threats.
The BlockWest read. Nadella’s admission is not a call for slower patching or a retreat from automated deployment. Rather, it exposes the inadequacy of decades-old infrastructure that was never designed for networked operation. The real problem lies upstream: systems like chillers and transportation firmware were built in an era before continuous updating existed, and retrofitting security onto them requires architectural redesign, not faster patches. That modernization will take years and capital neither the government nor private sector has fully mobilized to deliver.
The question now is whether companies will invest in replacing unpatchable legacy systems or whether they will accept the risk as the cost of maintaining installed infrastructure. Nadella mentioned the need to “modernize for sure” and to assess threat vectors in real time, but offered no timeline or specific commitment to decommissioning vulnerable hardware. Watch for whether Microsoft and other technology leaders will fund or accelerate industry standards for firmware updates in devices currently left behind by the patch cycle.
BlockWest is a news publication. Nothing here is investment advice. Read our disclaimer and editorial policy.
