← Blog

AI Is Finding Security Holes Faster Than Ever. Plan Your 2027 Security Budget Now.

If it feels like there’s a new “patch this now” warning every week, you’re not imagining it. In the last month alone, we’ve seen critical holes in PHP, nginx, the Linux kernel and Ruby, a hijacked marketing tool that put malicious code on 178 major brands’ websites, and a $6.3 billion theft that started with one engineer installing one file.

There’s a common thread, and it’s going to shape how every organization should think about security in 2027.

AI is finding the holes, on both sides

AI tools are now very good at reading code and spotting weaknesses. Security researchers are using them to find bugs that sat unnoticed for a decade. Attackers are using the same tools to find, and use, those bugs faster.

The numbers show it. Akamai reports that published vulnerabilities (CVEs) have climbed from roughly 4,000 a month through 2025 to about 17,000 a month by October 2026. Microsoft’s 2026 Digital Defense Report projects a record of around 72,000 CVEs this year, and says the typical time from a flaw being found to attackers using it has dropped well below 24 hours. Google’s threat team reported a case where attackers exploited a flaw found by an AI research agent within four days of it going public.

More bugs found is a good thing in the long run. In the short run, it means the window between “a fix is available” and “someone is using this against you” is now measured in hours, not months.

What’s been announced in the last few weeks

A quick tour of the big ones, in plain English:

  • PHP2Shell (October). Two flaws in PHP, the language behind WordPress and a huge share of the web, let an attacker run their own code on a server without logging in. Attackers were using them in the wild within days, and CISA added both to its list of known exploited vulnerabilities on October 26. Fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
  • A Linux kernel flaw chained with PHP2Shell. CISA added a Linux kernel bug nicknamed “Fragnesia” (CVE-2026-46300) to its exploited list on October 28. Attackers are pairing it with PHP2Shell: get in through PHP, then take full control of the server through the kernel. The kernel fix has been out since May, which tells you how many servers never got it.
  • nginx2root (announced November 18). nginx is the web server in front of a large share of the internet. Five new flaws, led by a critical HTTP/2 bug present in every release since 2015, can let an attacker crash the server or run code on it. A public proof of concept already exists. Fixed nginx versions are out (1.31.9 and 1.30.7); as of the announcement, some Linux distributions were still preparing their packaged fixes.
  • Ruby security releases (November 18). Ruby 4.0.10, 3.4.13 and 3.3.14 fix several vulnerabilities in regular expression and string handling. If you run a Ruby on Rails application, this one belongs on the list too.

It’s not just your servers: the Optimizely attack

On November 16, attackers abused a weakness in the account sign-up process of Optimizely, a popular website testing and personalization tool, and slipped malicious JavaScript into its customers’ website code. Researchers counted 178 organizations affected, including Zoom, the BBC, CNN, HSBC and GitLab.

For somewhere around 16 to 19 hours, visitors to those sites were loading code that skimmed card numbers typed into payment forms, swapped cryptocurrency wallet addresses for the attackers’, and sent cookies and page screenshots to the attackers. Optimizely says it closed the hole, removed the code and reset affected accounts.

The lesson: every third-party script on your site (analytics, chat, A/B testing, ad tags) runs with the same trust as your own code. If one of those vendors is compromised, your site is too. Researchers testing affected sites found that a properly configured Content Security Policy would have blocked the attack, but most of the sites they checked either didn’t have one or had one that still let the code through.

And it’s not just software: the Binance heist

On November 3, Binance published how attackers stole about $6.3 billion from the crypto exchange; the FBI attributed it to North Korean hackers.

It didn’t start with a server bug. It started with a fake recruiter. A Binance engineer was approached about a new job, went through interviews, and in the second one was asked to download a “coding assignment.” That assignment was custom malware that their security software didn’t catch. From that one computer, the attackers worked their way into Binance’s systems.

This is the part every business owner should sit with. The most expensive hack of the year so far began with someone being convinced to install something on their own computer.

What this means going forward

Starting now, every organization needs to treat these as ongoing habits, not one-time projects:

  1. Patch fast, and keep patching. Servers, hosted systems, laptops, phones, plugins, frameworks. Critical updates should go on in days, not “next quarter.” If you can’t say who applies patches to your website and servers and how quickly, that’s the first gap to close.
  2. Know what’s running on your site. Keep a list of every third-party script and plugin, remove what you don’t use, and put a Content Security Policy in place so an unexpected script can’t load or send data out.
  3. Be careful what you install. Don’t run files, “assignments”, browser extensions or tools from people you don’t know, even when the story sounds legitimate. A job offer, an invoice or a shared document is exactly what an attacker will send.
  4. Treat attachments and links with suspicion. PDFs, documents and links in emails from people you weren’t expecting to hear from are still the easiest way in. When in doubt, check with the sender another way before you open it.
  5. Have backups and a way back. When something does get through, tested backups and monitoring are what turn a crisis into an inconvenience.

Plan for more security spending in 2027

Here’s the honest version: security is going to cost more in 2027 than it did in 2025, for nearly everyone. Faster discovery means more patches, more often, and less room to put them off. Budgets built around a once-a-year checkup won’t keep up.

That’s not a reason to panic. It’s a reason to plan. Put patching, monitoring, backups and staff training in your 2027 budget now, rather than paying for a cleanup later.

If you’re not sure where your website, servers or applications stand, reach out to our team. We’ll help you figure out what needs attention first.


Sources: Help Net Security on PHP2Shell · watchTowr on PHP2Shell exploitation · Tenable on nginx2root · The Hacker News on nginx · Fragnesia and PHP2Shell chaining · Ruby 4.0.10 release notes · The Record on Optimizely · Help Net Security on Optimizely · Newsweek: affected organizations · The Washington Post on Binance · BleepingComputer on Binance · Akamai on the CVE surge · Help Net Security on Microsoft’s report · Help Net Security on Google’s findings

Let's talk

Put this to work

Questions about applying this to your business? A 30-minute discovery call is the fastest way to find out.

Reach Out →

or call 517-455-7837

Related articles

Our Digital Marketers' 4 Strategies for GDPR and CCPA Compliance Feb 9, 2026 GDPR and CCPA: What Businesses Need to Know Nov 18, 2025 What Do GDPR and CCPA Mean for Users? Oct 14, 2025
Share in X f