Security vulnerabilities: why so many alerts in recent weeks?
PHP2Shell, Java4Shell and new PHP alerts: understand the announcements, the risks and how to keep your website protected.

Sur cette page5 sections
If you follow website security or internet news, you may have seen several alerts in recent weeks: PHP, Java, critical vulnerabilities and urgent patches. Why does it feel as though so many have appeared at once? And, more importantly, what does this mean for your business?
In the space of a month, from 21 October to 19 November 2026, the US NVD database recorded 15,538 published vulnerability entries. Not all of them relate to the web or the tools we use every day. But the volume is striking: over the same period in 2025, the database recorded 3,862. In this article, we’ll look at vulnerabilities that are particularly dangerous for the web: those affecting PHP and Java.
A look back at the vulnerabilities announced in recent weeks
As a reminder, PHP is a language that powers many websites: WordPress uses it, as do applications built with Laravel or Symfony. According to W3Techs, nearly 70% of websites whose server-side language is known use PHP.
Java is used to build business applications, including in banking, where business rules can be complex. OpenJDK is one of the environments that allow these applications to run. PHP and Java are therefore present in many services we use every day.
21 October: two PHP2Shell vulnerabilities. The PHP team publishes two critical advisories, CVE-2026-109618 and CVE-2026-109619, along with patches. Both flaws concern the way PHP handles certain situations in memory. Under favourable conditions, they can allow an attacker to execute commands remotely without logging in to the site.
23 October: a third PHP vulnerability. The European CERT reports CVE-2026-115560, which can allow remote command execution in an unusual configuration. The PHP team recommends a protective measure while awaiting the next patched release. This is a separate issue from the two PHP2Shell vulnerabilities.
26 October: attacks confirmed. The US agency CISA adds these two vulnerabilities to its catalogue of exploited vulnerabilities. PHP2Shell is therefore not just a risk demonstrated in a laboratory: the agency reports that the vulnerabilities are being exploited. That does not mean that all PHP websites have been compromised.
17 November: Java4Shell. Researchers at Calif present a vulnerability in OpenJDK. OpenJDK publishes an advisory and recommends updates. The vulnerability lies in a component responsible for decoding data, particularly during connections or file uploads. On certain hardware, and depending on how an application uses this component, malicious data can cause memory corruption, expose information or allow commands to be executed.
18 and 19 November: new PHP alerts. The PHP team announces new patches, then publishes its security advisories on 19 November, several of which are rated critical. Under certain conditions, some vulnerabilities can allow code to run with the PHP program’s permissions. The advisories identify patched versions for each release branch. Barely a month after PHP2Shell, updates once again need close attention.
Why can these vulnerabilities be serious?
A website can continue to appear normal while an intruder uses it without your knowledge. Some vulnerabilities allow commands to be executed on the server: the attacker can then act with the permissions of the compromised program and sometimes gain further access. This does not automatically mean full control of the machine, but the consequences can go well beyond an unavailable page.
Thousands of fake pages under your name
I have repaired a client’s website where attackers had installed a page generator for low-quality products. They exploited the site’s visibility to get thousands of pages indexed for their own benefit. The site could appear normal at first glance, while these pages occupied search results. If nobody notices, this can damage its visibility and credibility.
Your files, your customers and your reputation
Another client told me that their website had been used to host illegal images and videos. Hosting illegal content on your site can have disastrous legal consequences, especially if the attacker reports the files after uploading them.
Another scenario: files or confidential information are copied, encrypted or threatened with disclosure in order to demand a ransom. An exposed secret payment key can also be misused. An attacker could use it to take control of financial transactions on the e-commerce account.
Finally, attackers can use a company’s access and communication tools against it. Clients whose sites had been hacked told me that their own contacts had received defamatory messages, leading to negative reviews and a loss of trust. In all these cases, putting the site back online is not enough: you also need to understand what was exposed, remove unwanted access and rebuild trust.

Why does it feel as though alerts are multiplying?
These tools have evolved over many years, and some errors remain hidden for a long time. In the case of PHP2Shell, a memory-handling problem was reported in 2020 and found again during an audit in 2024. At the time, its exploitation had not been demonstrated and it had not been fixed.
Today, artificial intelligence is changing how researchers search for vulnerabilities. Researchers at Calif used it to explore PHP, find leads and build demonstrations using their own expertise. It can also help prepare patches. But attackers have access to these tools too: they can use them to look for vulnerabilities and try to exploit them more quickly.
In my view, we have not seen the last of these alerts. If AI speeds up research on both sides, we will need to keep monitoring our tools and respond quickly to avoid leaving websites exposed.
What about Cadarsir websites?
Cadarsir website applications use PHP, not Java. The Java4Shell vulnerability therefore does not affect them directly. A PHP alert, however, deserves our full attention: at Cadarsir, I do everything I can to resolve problems as quickly as possible and protect websites.
Above all, what matters is having someone who understands the problem, knows how to solve it and can do so quickly.
Maintenance also means preparing and repairing your tools
When an advisory is published, I check the affected components and their vendors’ recommendations. The appropriate patches then need to be applied and important functions checked: a website that displays correctly but whose contact form no longer sends enquiries is not truly fixed.
Maintenance also includes backups and incident preparation: knowing how to contain the problem, restore the service and address its cause. At Cadarsir, this ongoing support accompanies each website, with human checks before and after updates. Preventive maintenance keeps things in good order and anticipates problems, corrective maintenance fixes them, and ongoing development adapts the site: together, they reduce risks without eliminating them.
For more detail, I explain what website maintenance really covers.
https://openjdk.org/groups/vulnerability/advisories/2026-11-17
https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w
https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp
https://www.bbc.co.uk/news/articles/cke89jevqm1vo
https://www.paloaltonetworks.com/blog/cloud-security/java4shell-cve-2026-114938-risks-mitigations/
https://github.com/php/php-src/security/advisories
https://calif.io/php2shell/
https://services.nvd.nist.gov/rest/json/cves/2.0?pubStartDate=2025-10-21T00%3A00%3A00.000%2B00%3A00&pubEndDate=2025-11-19T12%3A00%3A00.000%2B00%3A00&resultsPerPage=1&noRejected
https://www.php.net/archive/2026.php
https://cert.europa.eu/publications/security-advisories/2026-018/
https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching
https://www.cisa.gov/stopransomware/ransomware-guide
https://services.nvd.nist.gov/rest/json/cves/2.0?pubStartDate=2026-10-21T00%3A00%3A00.000%2B00%3A00&pubEndDate=2026-11-19T12%3A00%3A00.000%2B00%3A00&resultsPerPage=1&noRejected
https://w3techs.com/technologies/details/pl-php




