entrustIT Insights

Critical PHP vulnerability: what UK businesses need to do now

Written by Tom Dodd | Oct 23, 2026, 8:43:37 AM

Last updated 23rd October 2026

Two vulnerabilities in PHP, which the NCSC describes as a critical security issue, could let attackers run commands on a web server without logging in (CVE-2026-109618 and CVE-2026-109619). The NCSC says all versions of PHP are affected. UK organisations should identify where PHP runs, starting with internet-facing systems, and update to the latest fixed version as soon as possible.

What is the PHP vulnerability?

On 21 October 2026, the National Cyber Security Centre (NCSC) urged UK organisations to take immediate action on a critical security issue affecting PHP. PHP has published a security update to fix two linked vulnerabilities.

Both relate to how PHP behaves when it runs out of memory. Under certain conditions, an attacker could use this to corrupt memory and achieve unauthenticated remote code execution. In plain terms, someone outside your business could potentially run commands on a server running PHP without needing to log in.

The issue has been fixed, but only organisations that apply the update are protected.

 

Is my business affected?

Possibly, even if you’ve never heard of PHP. It’s used by around 70% of the websites whose server-side language can be identified, according to W3Techs, and it’s built into many other products too. You might be running it through:

  • Your company website
  • A customer portal or booking system
  • A third-party application hosted on your behalf
  • A product or appliance with PHP built in

The NCSC says all versions of PHP may be affected, not just old ones, so don’t limit your search to outdated installations.

How do I find out if we use PHP?

Start with the systems that face the internet, as they carry the most risk. Then work through:

  • Your web developer or hosting provider: ask them directly which sites and applications run PHP, and which version
  • Your asset list or IT documentation, if you have one
  • Third-party software and suppliers: ask whether their products use PHP and when they’ll release a fix
  • The NCSC-NL inventory of software products with a PHP dependency, which may help you spot affected software

If nobody can give you a confident answer, treat that as the first problem to solve. Websites built years ago by an agency that no longer exists, or a system you assumed a supplier was looking after, are the places that tend to get missed.

 

What does the NCSC recommend?

The NCSC’s priority actions are:

  1. Identify where PHP is running, prioritising internet-facing systems.
  2. Update to the latest version of PHP, and keep monitoring for further updates.
  3. If you can’t update yet, apply the temporary mitigations published by the PHP Foundation.
  4. If you can’t do either quickly, consider taking the system offline until it’s fully mitigated.
  5. If a system stays exposed, check it for signs of compromise, including backdoors, before you upgrade or mitigate. If you don’t have the skills in-house, an NCSC-assured Cyber Incident Response provider can help.
  6. Watch for vendor updates. Software and appliances that bundle PHP will need their own patches.

Frequently asked questions

Is my website at risk from the PHP vulnerability?
Possibly. The NCSC says organisations using any version of PHP are affected, and PHP runs a huge number of websites and web applications. If your website, customer portal or another system uses PHP and hasn’t been updated to the latest fixed version, it may be exposed. Internet-facing systems are the priority.

Do I need to update PHP?
Yes. The NCSC highly encourages all organisations to update to the latest fixed version of PHP, starting with internet-facing systems. Anyone on an older version should move to a fully supported one.

How do I know if my website uses PHP?
Ask your web developer or hosting provider which sites and applications run PHP, and which version. Check your IT documentation, and ask your suppliers whether their products include PHP. The NCSC-NL list of software products with a PHP dependency can also help you spot affected software.

Should I take my website offline?
Only if you can’t update or apply the PHP Foundation’s temporary mitigations quickly. The NCSC’s advice is to consider taking the system offline until it can be fully mitigated.

What are CVE-2026-109618 and CVE-2026-109619?
They are two linked PHP vulnerabilities that both relate to how PHP behaves when it runs out of memory. Under certain conditions, an attacker could use them to corrupt memory and achieve unauthenticated remote code execution. Both have now been fixed in updated versions of PHP.

Useful links