The gap between patching and exploitation is widest on enterprise network appliances: Microsoft’s telemetry puts the median time to fix a vulnerability on those devices at more than a year, while exploited flaws are increasingly weaponized within days. For security teams, the practical challenge is deciding which exposed systems need action before the routine patch queue catches up.
Microsoft Security Research analyzed roughly 383,000 CVEs disclosed from 1999 through September 2026. Its 2026 patching data shows a sharp difference by platform: about two weeks for Windows workstations, more than a month for Windows Server, over 10 weeks for Linux servers and macOS applications, and more than a year for network appliances.
“That gap is the threat actor’s window, widest on the critical systems that stay exposed the longest,” Microsoft researchers Yair Tsarfaty and Or Begam wrote in a blog post. Their comparison makes the operational mismatch plain: defenders may measure remediation in months, while attackers move on a much shorter schedule.
Why appliance fixes take longer
Network devices often sit at the center of business operations, which makes firmware changes harder to schedule than workstation updates. Cybersecurity researcher and red teamer Vibhum Dubey said change approvals, dependencies between applications, maintenance windows, and legacy infrastructure all delay remediation across enterprise environments.
“Network appliances are particularly difficult because firmware upgrades can affect critical business operations,” Dubey said. “In many cases, the challenge is not identifying vulnerabilities, but getting the right teams to remediate them without disrupting business services.”
That distinction matters for response planning. A vulnerability can be known and assessed while still waiting for the owners, outage window, or testing needed to deploy a fix. A monthly scan may identify the issue, but it doesn't resolve the scheduling bottleneck.
Exploit timelines keep shrinking
Microsoft’s figures point to a faster clock on the attacker side. Citing CISA data, the researchers said the mean time from CVE publication to inclusion in CISA’s Known Exploited Vulnerabilities catalog fell from 89 days in 2024 to 57 days in 2025. Through September 2026, the mean was 20 days and the median just three days.
VulnCheck’s State of Exploitation 2026 report found that 29% of exploits in 2025 began within one day of CVE publication. Microsoft also cited industry research linking advances in AI to shorter exploit development times. Some flaws may be exploited before public disclosure or before an organization has finished its initial review, Dubey said.
His proposed response is to shorten the exposure window with continuous monitoring, emergency patch procedures, virtual patching through web application firewalls and intrusion prevention systems, and clear ownership for remediation. “The priority should be to reduce the window of exposure, because by the time a vulnerability reaches the regular patching queue, attackers may already be exploiting it,” he said.
Exploited flaws aren't a representative sample
The vulnerabilities used in real attacks differ from the broader CVE pool. Server-side remote code execution accounts for 37% of exploited flaws, compared with 20% of all published CVEs. Local privilege escalation rises from 11% of published CVEs to 18% of exploited ones, while client-side remote code execution increases from 4% to 13%.
Other categories appear less often in observed attacks: cross-site scripting falls from 15% of published CVEs to 4% of exploited vulnerabilities, and denial-of-service flaws from 16% to 7%. Operating system vulnerabilities make up 23% of all CVEs but 41% of exploited ones. Windows is the most affected platform in Microsoft’s exploited-CVE data.
Remote code execution, authentication bypass, and local privilege escalation together account for 78% of vulnerabilities exploited in the wild. Microsoft’s researchers said the pattern reflects attackers’ preference for flaws that provide meaningful access or control.
Risk depends on access as well as severity
Microsoft frames attacker value around two factors: the impact of a successful exploit and the compromised asset’s exposure. Exposure includes the identities, privileges, and network connections reachable from that system. Servers can carry service accounts, application identities, or cloud-managed identities with permissions that extend access to sensitive data, administrative rights, and trusted networks.
Dubey said CVSS scores alone don't capture that context. He recommends prioritizing active exploitation, internet exposure, asset criticality, and reachable attack paths. A known exploit on an internet-facing system can deserve faster attention than a critical flaw on an isolated asset.
For security teams, the data points toward a more targeted patch queue: combine exploit activity with asset exposure and business impact, then route fixes to teams that can act quickly. That approach makes the longest patch delays visible before they become an attacker’s easiest route in.