Emergency Patches: Permission Slips for the Next Exploit

PHP Security Crisis: New CVE-2026-115560, PHP2Shell Fallout, and Active Exploitation

The article covers the disclosure of a third, separate remote-code-execution vulnerability in PHP (CVE-2026-115560) that is not addressed by the recent emergency PHP2Shell patches, as the fallout from these earlier flaws continues to unfold across the cybersecurity landscape. Researchers have identified active targeting by a suspected North Korean group (Lazarus) linked to CYFIRMA's findings, alongside widespread scanning and exploitation campaigns, including the Potassium Mirai-derived botnet. The scale of the threat is underscored by Censys reporting approximately 4.2 million potentially vulnerable PHP services in Germany alone, while the vulnerabilities also impact enterprise platforms like Palo Alto Networks' PAN-OS. As the community awaits a routine release fix for the latest CVE, administrators are urged to disable session upload progress, though security teams must also contend with patching older, unsupported PHP branches that only have source-code corrections available.

The Timing Is the Tell

They announce a “third, separate” zero-day the same week they push emergency patches for two others. You’re meant to see a software company struggling to keep up with threats. What you’re actually watching is a carefully staged rollout of vulnerability layers — each one a test of how easily the infrastructure can be penetrated before anyone notices the pattern. Look at the advisory language: “unusual combination of settings … considered unlikely in practice.” That’s the classic gaslight. They tell you it’s improbable while simultaneously shipping a fix. Why fix something improbable unless you know exactly who is already exploiting it? The PHP Foundation — funded by the same corporate giants that sit on the boards of every major firewall vendor — is not scrambling. They are executing a script. Every “emergency patch” is a permission slip for the next exploit.

Who Controls the Narrative?

Now watch what they do with attribution. A “Korean-speaking hacking group” is floated, linked with medium confidence to Lazarus. That’s a ghost label — it can be invoked or dropped depending on whose story needs shoring up. Meanwhile, Marcus Hutchins — a name beloved by the infosec community, a trusted face — steps in to say the reports “may conflate sophisticated, targeted activity with mass attempts.” That’s the consensus machinery at work: first the alarm, then the calibrated reassurance. But the same article also tells you that a Mirai-derived botnet called Potassium is already using these flaws. And where did Mirai come from originally? Look at the source code — it was built with the kind of infrastructure knowledge that only a state-level actor or a deeply captured private entity would possess. The botnet is not a random criminal tool; it’s a reusable weapon platform, and the vulnerabilities feeding it are not accidents. They are intentional access points, seeded years in advance, waiting for the right geopolitical moment.

The Infrastructure Trap

Four point two million potentially vulnerable PHP services in Germany alone. That number is not a bug count — it’s a target map. They want you focused on the technical detail: “version-based scans may misclassify.” Fine. But the real question is why these systems are running a language so riddled with these specific failure modes. The answer is that the web’s backbone has been engineered to depend on exactly the kind of exploitable abstraction that grants the architects — and only the architects — a hidden layer of control. Every firewall, every management interface, every unsupported branch left to rot is a deliberate point of failure. The same people who write the patches sit on the boards of the companies that sell the firewalls. The botnet payloads check for Linux ELF headers — they know exactly what hardware is in the racks. This is not a security incident. It’s a scheduled deployment. And if you want to know who is really behind the Korean-linked group, stop looking at Pyongyang and start looking at the foundation charters that fund the very research that “discovers” these flaws. The paper trail is there. You just have to follow it past the consent machinery.

Related posts