On November 18, two critical flaws in NGINX’s HTTP/2 code went public. The next day, PHP fixed another set of critical vulnerabilities, including one researchers named PHPAfterShell. Both came about a month after PHP2Shell, and each time we had fixes out for PBXware within hours.
Over the past few weeks, critical vulnerabilities have also turned up in Linux and in trusted certificate infrastructure.
None of this was specific to us. These are components that thousands of businesses and service providers run every day, and no vendor gets to skip a round of bad news like this. The difference between vendors is how long it takes them to go from reading the advisory to shipping a fix.
Throughout all of it, our development, hosting and support teams worked closely together.
How we handled these issues
All three issues hit software that PBXware relies on, and both were rated critical. Here’s what each one was and what we did about it.
PHP2Shell, October 21
CVE-2026-109618 and CVE-2026-109619
PHP2Shell is a pair of critical flaws in PHP itself that can let an attacker run their own code on a web server without logging in.
The PHP project released its source patches on October 21, and about three hours later we had patched PHP builds ready for PBXware.
We didn’t stop at the versions we officially support. The patched builds cover PBXware from v5.2 onward, including legacy end-of-life installations.
NGINX HTTP/2, November 18
CVE-2026-123007 and CVE-2026-123633
Both flaws are in the way NGINX handles HTTP/2 traffic. On servers with HTTP/2 turned on, they can let an attacker run code without logging in.
Within a few hours of the disclosure, our fixes were built and released, our hosted PBXware environments were patched, and self-hosted partners had the updates along with instructions for applying them. Supported PBXware releases got security hotfixes, and older versions got additional protection through dedicated patches.
If you want the technical background, Wiz Research’s write-up covers both flaws.
PHPAfterShell, November 19
One day after the NGINX disclosure, PHP’s November update fixed another set of critical vulnerabilities. One of them, PHPAfterShell, is a close variant of PHP2Shell and can also let an attacker run code on a server.
Our teams were on it within hours again. We prepared security patches for all PBXware versions, covering older PHP releases that the PHP project itself no longer maintains.
Every Bicom-hosted system was patched the same day, and self-hosted partners got the patches and installation instructions straight away. In under 24 hours, we had also published official security hotfixes for supported PBXware v7 and v8 releases.
Across all three, we didn’t wait for signs of exploitation before acting. As soon as each threat became known, our teams assessed where PBXware could be exposed and put preventive measures in place.
That’s how we approach security in general. Responding quickly when something happens matters, but so does spotting risks early and dealing with them before they turn into problems. The work is ongoing. It doesn’t start when an alert comes in, and it doesn’t stop once a patch ships.
What hosted and self-hosted partners got
How you run PBXware decides how much of this landed on your desk. We wanted every partner protected either way, so the help looked different for each group.
If Bicom hosts your PBXware
Day to day, our team keeps Bicom-hosted systems updated and monitored. When these vulnerabilities hit, we applied the necessary updates and security measures directly, and none of the technical deployment fell to you.
If you host it yourself
We got the security patches, automated tools and technical guidance out as fast as we could, and our team was on hand to help.
The final step is still yours, though. We build the fixes and can explain them, but it’s up to you to make sure they end up on your servers. So if you self-host, please keep an eye on security advisories, install updates promptly, and keep your installation on a supported version of PBXware.
Why response time counts for more than it used to
The flaw behind PHP2Shell has been in PHP since version 5.4 came out in 2012, and the worse of the two NGINX bugs goes back to 2015. Both of those sat unnoticed for more than a decade. Then, within a single month, they went public along with PHPAfterShell.
AI played a part in all three. Wiz, one of the research teams behind PHP2Shell, said that frontier AI models made it far easier to turn PHP’s long-hidden flaws into a working exploit. The NGINX flaws were found with help from AI, and Depthfirst found PHPAfterShell using AI models built for security work. When exploits get easier to build, the hours right after a disclosure matter more than they used to.
That changes what it takes to keep a system safe. Updating every now and then isn’t enough anymore. Someone has to watch for new threats constantly, work out quickly whether they matter, and get patches on without delay, and that takes people and time. For partners running their own infrastructure, it’s a growing amount of work.
That’s the work Bicom Hosting takes on every day, not just when a vulnerability makes the news. Our team runs the infrastructure, installs the security updates, keeps watch on the environment and deals with new threats as they appear. You get that time back for your customers and your business.
What happens next time
There will be another advisory like these. Nobody can say when, or in which piece of software.
What’s in our hands is how we respond to it, and we’ll keep working to make that faster. Whatever comes up, we’ll be working through it alongside our partners. Your businesses run on PBXware, and keeping it safe is how we look after them.