Blog

The ISVTEC blog: security flaws, incidents and lessons from managed infrastructure and DevOps, told with the real figures, including what is still left to do.

New PHP Flaws: Fix Installed for Our Clients the Next Day, With No Reboot

Five PHP flaws rated 9.2 out of 10 let an attacker take over a server. Our team installed the fix for our clients the very next day, with no reboot.

Learn more →

Java Flaws: Our Clients Informed the Day After the Fix, Install Planned With No Downtime

Two Java flaws rated 7.4 out of 10 expose the data of Java applications. Our team informed its clients the day after the fix came out and planned it in their maintenance window, with no downtime.

Learn more →

Linux Flaw "Fragnesia": Our Clients Protected in One Day, With No Downtime

An actively exploited Linux kernel flaw hands an attacker full control of a server. Our team closed the door the same day, with no reboot and no downtime.

Learn more →

WordPress: The Forgotten Copy Is the Open Door

An actively exploited WordPress flaw targets sites that are not up to date. Yours is. But what about the old staging site sitting on the same server?

Learn more →

Black Friday in 10 Days: Will Your Site Hold the Peak?

€290K in one day, 1,500 visitors at once, no slowdown: what we do before every e-commerce peak, and what can still be done in the 10 days left.

Learn more →

Your Servers No Longer Reboot While Your Customers Buy

New in the ISVTEC console: you set, for each server, the only time we may interrupt it. Reboots and planned interventions happen there, nowhere else.

Learn more →

Outlook Down for More Than 18 Hours: Would Your Site Survive the Same?

On 12 November, Outlook and Teams went down in 74 countries. The real risk is not a bad provider, it is a single one.

Learn more →

AI Finds Security Flaws Faster Than Ever: We Patch Faster Still

For a few weeks now, AI has been uncovering security flaws at scale. What we launched, preventively, to protect our clients' platforms.

Learn more →

PHP flaw CVE-2026-109618: our clients protected before the fix even existed

Critical PHP flaw of 21 October 2026: our clients protected that morning, before the official fix, then patched on every PHP version and operating system.

Learn more →