Patching has always mattered, but the timeline and urgency just changed. When a software vendor releases a new security update, that update leaves hints as to exactly what was previously broken. AI tools can now read that update, work out the flaw, and build a working attack against every device that hasn't installed it yet, with no human involved. The only real defense is reducing the gap between "patch released" and "patch installed" on every device you own, for both the operating system and every app running on it.
What just happened
On November 16, Google's Threat Intelligence Group and Mandiant reported finding an attacker's staging server running a multi-agent AI framework called exploit_agent. It watched popular software for new releases, compared the code before and after each security fix, drafted an exploit for the flaw that each fix addressed, and then ran it against systems that hadn't updated yet. Google described it as the first time it had seen that full chain automated in the wild.
The same server held data stolen from victims and scripts for what attackers do after they get in: internal reconnaissance, password guessing, and installing backdoors.
How a patch turns into an attack
Security researchers call it patch diffing. When a fix ships, an attacker compares the old version of the software with the new one, finds the lines that changed, and works backward to the vulnerability those lines were closing. Every device still running the old version is now a known target.
This isn't new. What's new is the speed at which it’s happening. Reverse-engineering a patch used to take skilled people weeks or months, and that delay is the reason monthly patch cycles and "I'll restart on Friday" felt reasonable. AI is collapsing that window to days, and in some cases hours. Google's researchers also suggested attackers may find it more efficient to chase flaws that already have a fix rather than to hunt for brand-new ones. Put simply, a published patch now doubles as a set of exploit instructions.
Your laptops are in scope too
The activity Google reported targeted web applications. But the technique works on anything with a published fix, and the software on your team's devices changes constantly.
Most of that exposure doesn't come from macOS or Windows. It comes from the third-party apps running on top of them: browsers, PDF readers, Zoom, Slack, and the rest. When we built our app patching policy, we looked at a year of release history. Microsoft Edge shipped an update roughly every 3.3 days on average, and Chrome roughly every 5.2. Each of those releases is a new map for whoever is looking. A browser that's two weeks behind isn't slightly out of date. It's several known, documented holes behind.
The weak point is rarely the patch itself. It's the gap between a fix being available and a fix being installed, and that gap usually comes down to people. Someone dismisses the prompt before a meeting. Someone else hasn't restarted in a month. An attacker only needs one of them.
Fast doesn't mean reckless
There's a fair counterargument, and anyone who has lived through a bad update has made it. Patches can break things. A rushed update can take a fleet offline just as surely as an attacker can, and the run of large-scale outages over the past couple of years has made plenty of IT leaders wary of moving too fast.
The answer isn't to slow patching down. It's to test before you enforce, then enforce on a short, predictable clock. Speed and stability only conflict when there's no process sitting between them.
How we handle patching at Advisory
Here's what that looks like across the Mac and Windows fleets we manage.
- OS updates have hard deadlines, enforced by the operating system. On Macs, we use Apple's Declarative Device Management (DDM) to set a required macOS version and a deadline, typically 15 days for minor updates. The Mac handles the download and reminders, holds off while someone is in a Zoom, Teams, Webex, or Google Meet desktop call, and installs and restarts on its own if the deadline passes. On Windows, devices get a 5-day grace period to restart on their own schedule before the update is enforced.
- Third-party apps are patched automatically. Common apps on Mac and Windows update to the vendor's latest release on a set cadence: web browsers within 5 days, other apps within 7. Closed apps update quietly in the background. Open apps prompt the user, and on Macs, five deferrals is the limit before the update is required.
- Big changes get more runway. Major macOS upgrades are held for 90 days by default so we can confirm compatibility first. Version-pinned developer and engineering tools are deliberately left out of auto-patching, because silently updating them can break a working build instead of protecting it.
- Exceptions are documented, not quiet. When someone needs an update postponed for a real reason, it's requested in writing, tied to that reason, and reviewed, instead of a device quietly falling behind.
Questions worth asking about your own patching
If you're a leader trying to gauge where your company stands, these will tell you quickly:
- How many days does it take for a new OS security update to reach 95% of our devices?
- Are browsers and other third-party apps patched automatically, or only when someone remembers?
- What happens when an employee ignores update prompts for two weeks?
- Can we produce a report showing patch status for every device today?
If any of those answers is "I'm not sure," that's worth fixing before an auditor, an insurer, or an attacker comes knocking at your door. SOC 2 audits, cyber insurance renewals, and client security questionnaires all ask how fast you patch, and "we ask people to update" is no longer a good answer.
If your team can't say how many devices are running last month's browser, patching is probably running on reminders instead of enforcement, or not at all. That's exactly the kind of gap an environment audit surfaces early, and it's one of the first things we look at.
If you’d like to talk through the steps to increasing your security or preparing for an audit, contact us to get started.
