For decades, finding a serious bug in PHP, nginx or Node.js took a rare kind of expert and weeks of patient work. In 2026 that changed. AI models now read source code, spot memory-safety bugs and even write working exploits, at a scale no human team can match. This autumn the result landed on everyone's servers: emergency patches for the language behind most websites, for the web server in front of them, and for the runtime many modern apps are built on.
The good news is that most of these bugs were found by the defenders first. The bad news is that the gap between "found" and "exploited" has almost disappeared. If you run a website, this is the moment to know exactly what you're exposing to the internet.
Key takeaways
- AI is now a serious bug hunter. Anthropic's Project Glasswing, OpenAI- and Google-backed research and independent firms like Calif and Wiz all used frontier models to find critical flaws in widely used open-source software this year.
- PHP had its worst security moment in years. Two critical bugs, together called PHP2Shell, allowed remote code execution before login. Attacks started within hours of disclosure, and CISA added both to its list of actively exploited vulnerabilities.
- nginx and Node.js were hit too. nginx got three critical fixes in October (CVSS 9.2), and Node.js fixed 16 vulnerabilities on 11 November, five of them found with Claude.
- Patching is the bottleneck, not discovery. AI finds bugs faster than maintainers can fix them and faster than most companies install updates.
- The practical defence is boring and effective: know which software versions you run, patch fast, don't advertise versions you can't patch, and keep monitoring.
2026: the year AI started finding the bugs
On 7 April 2026, Anthropic announced Project Glasswing, an initiative to find and fix vulnerabilities in critical software using an unreleased model, Claude Mythos Preview. Its launch partners include AWS, Apple, Google, Microsoft, Cisco, CrowdStrike, the Linux Foundation and Palo Alto Networks. Anthropic says the model found thousands of high-severity vulnerabilities, some in every major operating system and web browser, including a 27-year-old OpenBSD flaw and a 16-year-old FFmpeg bug that automated tests had executed five million times without noticing.
By late May, Anthropic reported that Glasswing had helped uncover more than 10,000 high- or critical-severity vulnerabilities. That's where the real problem showed. Of the open-source findings reviewed so far, only 97 had been patched upstream at that point. Finding bugs had become cheap; fixing them hadn't.
Anthropic didn't hide the downside. The same capabilities that help defenders also lower the bar for attackers. As CrowdStrike's CTO put it on the Glasswing announcement: "the window between a vulnerability being discovered and being exploited by an adversary has collapsed."
And it's not just Anthropic. OpenAI and Google models were behind this autumn's biggest PHP story, and security firms now routinely credit AI in their advisories. Earlier this year Claude also found 22 vulnerabilities in Firefox in two weeks.
PHP2Shell: the PHP bug that hit "70% of the web"
PHP runs WordPress, Drupal, Joomla and a huge share of all websites. On 21 October 2026, the PHP project shipped emergency releases (8.5.12, 8.4.27, 8.3.36 and 8.2.35) for two critical memory-safety bugs, CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell.
What made them so serious, according to Wiz Research:
- No login needed. Researchers demonstrated remote code execution against the latest WordPress, Drupal and Joomla images.
- Old versions too. Every PHP version released in the last decade was affected by at least one of the bugs, going back to PHP 5.4.
- Data leaks even without a takeover. The memory-disclosure part could leak passwords, tokens, API keys and certificates from a plain "Hello World" app.
AI was central to the discovery. Fortune reports that the security firm Calif found the first issue on 1 August using OpenAI's GPT-5.6 Sol, and that Wiz independently found its first issue on 19 August using Google's Gemini 4 Argon, GPT-5.6 Sol and its own tooling. OpenAI coordinated a coalition with PHP, Wiz, Calif, Cloudflare and others to get the fix out.
Then the race started:
- Cloudflare saw tens of thousands of exploit attempts within 45 minutes of the news, and millions by that evening.
- Amazon says attackers began targeting PHP2Shell four days before the patches were released.
- On 26 October, CISA added both CVEs to its Known Exploited Vulnerabilities catalogue and ordered US federal agencies to secure their systems within days.
If your site runs an unpatched PHP version, assume it's being probed right now. PHP 8.1 and older are end-of-life and don't receive these fixes at all.
nginx: the web server in front of almost everything
nginx sits in front of a huge number of websites, often as a reverse proxy for PHP or Node.js apps. It had a busy year too.
Found with Claude. In March, Calif reported CVE-2026-27654, a heap buffer overflow in nginx's WebDAV module that let an attacker read or write files outside the intended folder. F5's advisory credits Calif "in collaboration with Claude and Anthropic Research." Calif's write-up is a good look at how this works in practice: Claude flagged the bug and built working proofs of concept, while humans corrected its arithmetic and picked the realistic attack path. It was fixed in nginx 1.29.7. It only affected setups with WebDAV COPY/MOVE combined with alias.
Three critical flaws in October. On 21 October, F5 released fixes for three critical nginx vulnerabilities, each scored CVSS 9.2:
| CVE | What it is | Where |
|---|---|---|
| CVE-2026-15176 | Heap buffer overflow | alias and rewrite handling |
| CVE-2026-97205 | Use-after-free | Asynchronous file I/O (AIO) and Server Side Includes |
| CVE-2026-93479 | Heap buffer overflow | map directive |
All three can be triggered by an unauthenticated remote attacker. They can crash workers, and in some configurations lead to remote code execution. Affected: nginx Open Source up to 1.30.5 and 1.31.6, NGINX Plus R33–R37, and several F5 NGINX products such as the Ingress Controller.
And this month: NoisyTCP. Not an nginx bug, but it hits nginx servers: a Linux kernel flaw (CVE-2026-99288) lets attackers crash servers with crafted TCP traffic, including default nginx, Apache and SSH setups. The fix is a kernel update and a reboot.
Node.js: 16 fixes, five found with Claude
On 11 November 2026, Node.js released 26.13.1, 24.22.3 and 22.23.5, fixing 16 vulnerabilities, seven of them rated high. Most were in HTTP/2 and TLS, the parts of Node that face the internet directly.
Five were reported by security researcher Chris Rohlf "in collaboration with Claude and Anthropic Research." Two stand out:
- CVE-2026-123864 (high): an HTTPS flaw that could leak server memory into a request body.
- CVE-2026-123863 (high): a way for a remote client to crash an HTTP/2 server.
Node.js published no workarounds. Upgrading is the fix.
What this means for your website
You don't need to run a bank to be affected. A typical small business website runs PHP (because it's WordPress), sits behind nginx (because the host set it up that way), and maybe has a Node.js app or API next to it. Most owners don't know which versions they run, or whether their hosting provider has patched them.
Three things have changed:
- Bugs are found faster. AI makes discovery cheap for researchers and attackers alike.
- Exploitation starts almost immediately. With PHP2Shell, attacks started before the official patch and scaled to millions of attempts within a day.
- Attackers scan everything. Automated tools don't care whether you're a multinational or a local shop. If your server advertises a vulnerable version, it's on a list.
What to do this week
- Know your versions. Find out which PHP, nginx and Node.js versions you run, including on servers your hosting provider manages. Don't guess.
- Patch PHP now. Move to at least 8.5.12, 8.4.27, 8.3.36 or 8.2.35. If you're on PHP 8.1 or older, plan the upgrade. Those versions get no fixes.
- Update nginx and Node.js to the fixed releases above, and update your Linux kernel for NoisyTCP.
- Stop advertising versions. Turn off
server_tokensin nginx andexpose_phpin PHP, so scanners can't read your exact versions from every response. - Get the basics right: HTTPS everywhere, security headers, and email protection (SPF, DKIM, DMARC) so nobody can send mail as you.
- Keep watching. One check is a snapshot. New CVEs appear every week, and your site changes too.
How Delta Security helps
We built Delta Security because most companies have no idea what their website shows the outside world, and finding out shouldn't take a pentest.
- A free check in about a minute. Enter your web address and you get a grade from A to F, a score out of 100 and a plain-language summary. No account needed.
- Around 20 passive checks. It looks at your site the way any visitor's browser does: HTTPS and TLS, security headers, cookies and trackers that load before consent, email authentication (SPF, DKIM, DMARC), DNS settings, and outdated software, which it compares against known-vulnerability sources such as OSV.dev, CISA's Known Exploited Vulnerabilities catalogue and EPSS.
- Monitoring for €5 a month. A monthly rescan, the full report and your grade over time, so you notice when something slips.
- We fix it, if you want. With the maintenance plan (from €250 a month on an annual plan), our own engineers handle patches, code review, monitoring and priority fixes.
To be clear about what it is: Delta Security is a passive scan. It doesn't try passwords, hunt for hidden pages or attack anything, and it doesn't replace a full security audit. It can only flag what's visible from the outside. But that is exactly what automated attackers look at first.
Check your website for free at delta.codingdelta.com, or talk to us if you'd rather have us look at it together.
Sources
- Anthropic: Project Glasswing
- The Hacker News: Claude Mythos AI finds 10,000 high-severity flaws
- Wiz Research: PHP2Shell: critical RCE vulnerabilities in PHP
- Fortune: AI tools discovered the PHP vulnerability that could take down 70% of the internet
- BleepingComputer: CISA confirms PHP2Shell vulnerabilities now exploited in attacks
- Calif: Claude + Humans vs nginx: CVE-2026-27654
- CSA Singapore: Critical vulnerabilities in F5 NGINX products
- BleepingComputer: NoisyTCP Linux kernel flaw
- Node.js: November 2026 security releases
- TechCrunch: Claude found 22 vulnerabilities in Firefox over two weeks
Curious what this could do for you?
We're happy to think along — over coffee on the Keizersgracht or on a video call.
