PHP2Shell just handed every MSSP two problems at once.
CVE-2026-109618 and CVE-2026-109619 are unauthenticated RCE flaws in PHP itself, not a plugin, so they sit underneath a huge share of the web apps your customers run. Patches landed October 21, but attackers didn’t wait. Amazon’s MadPot honeypot logged an exploitation attempt on October 17, public PoCs are circulating, and PHP 7.3 and older, including PHP 5, have no fix at all.
The squeeze
- Existing customers want answers today: Are we exposed? Were we hit before we patched?
- New inbound IR requests are arriving from organizations that aren’t your customers yet, and they won’t wait in your queue.
- The same analysts are handling both.
Patching closes the door. It doesn’t tell you who already walked through it. Every “we’ve patched” conversation turns into a “were we compromised?” conversation, and that question doesn’t scale with manual collection and one-box-at-a-time triage.
Why “we’ve patched” isn’t the end of the conversation
Patching closes the door. It doesn’t tell you who already walked through it.
With exploitation starting before disclosure, every “we’ve patched” conversation becomes a “were we compromised?” conversation. Answering that means looking at every exposed web server for webshells, unexpected child processes, new persistence and outbound connections that shouldn’t exist.
That question doesn’t scale with manual collection and one-box-at-a-time triage. If each investigation means an analyst logging into a server, pulling artifacts by hand and reviewing them in isolation, your capacity caps out long before the requests do.
Answering “were we hit?” at scale
Remote evidence collection changes the maths. Instead of one analyst working one server at a time, the same analyst can sweep hundreds of servers at once and review the results in one place. With Binalyze AIR, MSSP teams can:
- Collect forensic evidence remotely from Windows, Linux and macOS web servers, without waiting for site access.
- Sweep hundreds of endpoints for indicators at once using YARA, Sigma and osquery rules, with evidence and findings kept together for review.
AIR automates the collection and the repetitive groundwork. Your analysts keep the judgement. That’s what lets the same team cover your existing book of business and the new IR engagement that shows up on Friday night.
Turn the spike into a service
Every major vulnerability brings a wave of “were we hit?” questions. MSSPs that can answer them quickly and consistently win the follow-on work: retainers, assessments and longer-term IR relationships. PHP2Shell won’t be the last one.
In the next post, we break down a three-step PHP2Shell compromise assessment you can run with AIR today.
If PHP2Shell is about to double your caseload, let’s talk.


