PHP2Shell vulnerabilities. Fixes and hosting checks

A working website does not confirm its PHP patches. Check both CVEs with your administrator and agree on ongoing server maintenance.

In this article
  1. What PHP2Shell means
  2. Which releases contain the fixes
  3. Five questions for your administrator
  4. What a public scan can confirm
  5. The researchers and the role of AI
  6. Plan for the end of support
  7. Questions from website owners

In short

PHP2Shell covers two critical PHP vulnerabilities. Fixes were released on 21 October 2026. Ask your administrator to confirm both fixes in the environment serving your website. A working form, HTTPS or a public scan result cannot confirm this.

Your website looks normal. Does the PHP running it have the PHP2Shell fixes?

A business owner usually does not need to update the server personally. You do need a clear answer from whoever maintains it. Here are the vulnerability references and questions for your hosting provider.

What PHP2Shell means

The name covers CVE-2026-109618 and CVE-2026-109619. Both have a CVSS 4.0 score of 9.2. Under certain conditions, they allow remote code execution without logging in.

The first technical advisory describes problems handling memory exhaustion. PHP can treat invalid memory state as valid data.

The second advisory concerns internal state left from an earlier request. A later request can access memory that has already been freed. This can lead to code execution, beyond simply exposing data.

Risk depends on the version, configuration and how PHP handles requests. A demonstration on Apache with mod_php reached the vulnerable code before the application started. Other ways of running PHP also need patch checks.

Which releases contain the fixes

These were the first releases fixing both CVEs, published on 21 October 2026.

PHP branchRelease containing the fixes
8.28.2.35
8.38.3.36
8.48.4.27
8.58.5.12

The numbers come from the technical advisories linked above. They are reference points for these two vulnerabilities. They do not mean a release is free from every other security issue.

Your administrator should check current updates for a supported branch compatible with the application. The PHP announcement archive also contains a later session handling advisory from 23 October.

A system vendor may backport fixes into an older package. The PHP version number alone then cannot settle the question. Ask for the package identifier and a vendor notice confirming both CVE fixes.

Five questions for your administrator

  1. Which PHP package serves this specific website, and when was it checked?
  2. Does it contain fixes for CVE-2026-109618 and CVE-2026-109619?
  3. Were the processes serving requests restarted after the update?
  4. Were forms, login and important operations tested after the change?
  5. Who manages future updates and the branch’s end of support?

The terminal’s PHP version can differ from the one serving your website. With Docker, new containers must run the patched image. Building an image alone does not change the running application.

Prepare a checked backup and tests for important operations before updating. If you suspect an earlier breach, request a separate review of evidence and logs. Installing a patch does not prove nobody previously gained access.

What a public scan can confirm

Our website scan checks items including security headers and the TLS certificate. It does not attempt to exploit PHP2Shell. It cannot confirm installed patches or rule out a breach.

Checking the package and running version requires administrative access. Agree on access and maintenance responsibility during website handover.

The researchers and the role of AI

The PHP Foundation describes the investigation and fixes. Researchers reporting issues included Calif, OpenAI and Wiz. AI also helped validate reports, while people made decisions and worked on patches.

Plan for the end of support

The PHP support schedule ends upstream security support for PHP 8.2 on 31 December 2026. The PHP2Shell patch does not extend that date. Plan an upgrade or separately verified vendor support.

Questions from website owners

Does updating WordPress fix this?

It does not confirm a PHP update. The application and server environment have separate versions. Check both.

Does HTTPS protect against PHP2Shell?

HTTPS protects the connection. It does not remove vulnerabilities in the PHP running on your server.

Does an older version number always mean an unpatched server?

Vendors can backport fixes. You need confirmation for the specific package and both CVE references.

Can configuration changes replace an update?

The PHP advisories describe limits on particular attack paths. Do not treat these measures as a complete replacement for the patches.

Can we close the issue after patching?

Confirm the running environment, test important functions and assign ongoing maintenance. Signs of a breach require a separate investigation.

If nobody is responsible for your website maintenance, describe the situation in the form below. Leave out passwords and logs containing customer data.

What would you like to change in your business?

Leave your number. We will talk about your process and see whether we can help. The first call is free.

When is the best time to call?
Controller: Oleksandr Bondarenko (BondSoft)Privacy PolicyTerms of Service
Legal details

The data controller is Oleksandr Bondarenko, trading as Oleksandr Bondarenko Software Solutions (BondSoft), ul. Jana Heweliusza 11, 80-890 Gdańsk, Poland, NIP 5833576264, e-mail: office@bondsoft.pl.

We process your data solely to contact you about your enquiry and to present an offer — on the basis of your consent (Art. 6(1)(a) GDPR and Art. 398 of the Polish Electronic Communications Law) and our legitimate interest in handling the enquiry (Art. 6(1)(f) GDPR).

Providing the data is voluntary but necessary for us to reply. You may withdraw your consent at any time by writing to office@bondsoft.pl — this does not affect the lawfulness of processing before the withdrawal.

You have the right to access your data, rectify it, erase it, restrict its processing, transfer it, and lodge a complaint with the President of the Polish Personal Data Protection Office.

Full information: Privacy Policy.

Send us an email

The service this text is about

Websites

A website made for your company, not from a template. Before you pay, we show a working prototype.

Check it on your sitePage speed