Skip to main content

Critical Alert

Talion Security Advisory

Industry News

Talion Security Advisory

Critical PHP Vulnerabilities: Immediate Action Required to Protect Your Systems

Severity: CRITICAL | CVSS 9.2
Vulnerabilities: CVE-2026-109618 and CVE-2026-109619

What You Need to Know

Get Help Now

By submitting this form, you agree to receive communications from Talion Cyber Security and agree to our Privacy Policy.

What Has Happened?

The PHP development team has released security updates addressing two critical vulnerabilities affecting the PHP runtime environment.

Both vulnerabilities relate to how PHP handles memory and internal processing during web requests. Under certain conditions, attackers may be able to exploit these weaknesses to execute code on an affected server without requiring valid login credentials.

The vulnerabilities are identified as:

CVE-2026-109618 — Memory Corruption During Error Handling

This vulnerability affects how PHP handles memory when a request encounters an out-of-memory condition. An attacker may be able to exploit the resulting memory corruption to achieve remote code execution.

CVE-2026-109619 — Improper Handling of Internal Request State

This vulnerability involves internal PHP data remaining accessible after its underlying memory has been released. Under certain conditions, this could allow an attacker to execute unauthorised code through subsequent requests.

Both vulnerabilities have been assigned a critical CVSS score of 9.2.

The significance extends beyond individual websites. PHP is embedded in numerous business applications, content management systems and web services, meaning organisations may have exposure even where PHP is not directly managed by their internal IT teams.

Which Systems Are Affected?

Organisations running PHP-based applications should review their environments immediately, particularly internet-facing services.

Affected PHP versions and required actions

PHP version Affected releases First fixed release Recommended action
PHP 8.5 8.5.0–8.5.11 8.5.12 Update immediately
PHP 8.4 8.4.0–8.4.26 8.4.27 Update immediately
PHP 8.3 8.3.0–8.3.35 8.3.36 Update immediately
PHP 8.2 8.2.0–8.2.34 8.2.35 Update immediately
PHP 8.1 and older Unsupported upstream No fix in these branches Migrate to a supported, fixed release

Affected environments may include websites, web applications, content management systems, customer portals and third-party products incorporating PHP.

Organisations should also review containers, hosted environments and applications maintained by external technology providers.

The presence of PHP does not automatically mean a system has been compromised. However, organisations should not assume that an application is protected simply because its software, plugins or other components are up to date. The underlying PHP runtime must also be assessed.

Why These Vulnerabilities Matter to Your Business

A successful remote code execution attack can give an attacker the ability to run unauthorised commands within the permissions of an affected service.

Depending on the system configuration and security controls in place, the consequences could include:

  • Unauthorised system access: Attackers may gain access to application environments and supporting infrastructure.
  • Data exposure: Sensitive business information, credentials or customer data could become accessible.
  • Operational disruption: Compromised services may experience outages, instability or deliberate interference.
  • Further compromise: Attackers may attempt to establish persistence or move into other connected systems.
  • Financial and reputational impact: Investigation, recovery, service disruption and potential regulatory obligations can create significant business costs.

The immediate concern is not simply the existence of a vulnerability. It is whether an organisation can identify its exposure, remediate affected systems and determine whether malicious activity has already occurred.

For organisations with complex infrastructure, multiple application owners or outsourced technology environments, establishing that visibility can be challenging.

What Should Organisations Do Now?

The NCSC recommends immediate action to identify affected systems and apply the latest security updates.

Talion recommends the following response priorities.

Immediate security response priorities

Priority Action What the organisation should establish
1. Identify Inventory PHP deployments Which systems are exposed?
2. Remediate Patch or apply vendor fixes Have vulnerable installations been secured?
3. Investigate Review logs and security telemetry Is there evidence of exploitation?
4. Contain Isolate potentially compromised systems Can further attacker activity be prevented?
5. Verify Validate remediation and monitoring Has exposure been reduced and response completed?

1. Identify PHP Across Your Environment

Establish which websites, applications, servers, containers and third-party platforms use PHP.

Prioritise internet-facing systems, business-critical applications and services processing sensitive information.

2. Apply the Latest Security Updates

Update affected PHP installations to a fixed, supported version.

Where PHP is supplied through a managed hosting provider, operating system distribution or third-party application, confirm the vendor’s remediation guidance and whether a security fix has been applied.

Updating PHP is the only complete remediation for these vulnerabilities. Temporary mitigations should not be treated as equivalent protection.

3. Assess Systems for Potential Compromise

Review relevant web server, application, endpoint and security monitoring data for suspicious activity.

Investigations should consider unexpected processes, unauthorised files, unusual outbound connections and other indicators that may suggest exploitation.

Where compromise is suspected, preserve relevant evidence and involve incident response specialists before undertaking potentially destructive remediation.

4. Apply Temporary Risk Reduction Measures Where Necessary

Where immediate patching is not possible, review the temporary mitigations published by the PHP security team.

These measures may reduce exposure to particular attack paths but do not eliminate the underlying vulnerabilities.

Organisations unable to patch or adequately mitigate exposed systems should consider isolating or temporarily disabling affected services until remediation is possible.

5. Verify Remediation and Maintain Monitoring

Confirm that updates have been applied successfully and that affected services are operating as expected.

Continue monitoring for suspicious behaviour, particularly where systems were exposed before security updates became available.

Patching addresses the known vulnerability. It does not, by itself, establish whether a system was previously compromised.

Why Continuous Security Monitoring Matters

Critical vulnerabilities highlight an important distinction between vulnerability remediation and cyber threat detection.

Vulnerability management helps organisations identify, assess and prioritise weaknesses. Security monitoring helps determine whether those weaknesses are being targeted or exploited.

Both capabilities are necessary.

An organisation may successfully deploy a security update while remaining unaware of suspicious activity that occurred before remediation.

Equally, an organisation may have sophisticated security monitoring but remain exposed because critical vulnerabilities have not been identified or addressed.

An effective response brings these capabilities together through coordinated vulnerability management, threat intelligence, detection, investigation and incident response.

This is particularly important where security responsibilities are distributed across internal IT teams, hosting providers, application developers and external security partners.

How Talion Can Help

Talion works with organisations to strengthen cyber defence through managed security operations, threat detection, vulnerability management and specialist security expertise.

In response to critical vulnerabilities such as these, Talion’s capabilities can support organisations in several areas.

Vulnerability Management

Identify and prioritise security weaknesses, improve visibility of exposed assets and support risk-based remediation decisions.

Managed Detection and Response

Monitor relevant security telemetry, investigate suspicious activity and support coordinated response to potential threats.

Hybrid Security Operations Centre

Combine Talion’s security expertise with existing internal teams, tools and processes to strengthen continuous monitoring, escalation and response.

Incident Response

Support investigation, containment and recovery where malicious activity or system compromise is suspected.

Security Advisory and Testing

Assess security controls, identify gaps and help organisations strengthen their resilience against emerging threats.

Talion’s approach is designed to complement existing security investments while maintaining transparency, operational accountability and organisational control.

Don’t Wait for a Vulnerability to Become an Incident

The discovery of these PHP vulnerabilities is another reminder that the time between public disclosure and potential exploitation can be short.

Organisations need more than a patching process. They need visibility of exposed systems, the ability to detect suspicious activity and clear responsibilities for responding when threats emerge.

If your organisation is concerned about exposure to these vulnerabilities, or needs support strengthening its security monitoring and response capabilities, Talion can help you assess the next steps.

Speak to Talion’s Cyber Security Team

Contact Talion

Useful Resources and Official Security Guidance

Organisations responding to the recently disclosed PHP vulnerabilities should consult the following authoritative resources for technical details, security updates and recommended actions.

Official Vulnerability Information

PHP Security Advisory — 21 October 2026

The PHP development team’s official announcement covering CVE-2026-109618 and CVE-2026-109619, including affected releases, technical details and remediation guidance.

UK National Cyber Security Centre — Critical Security Issue Affecting PHP

UK government guidance outlining the security risks and recommended actions for organisations operating PHP-based systems.

Security Updates and Remediation

PHP Official Downloads

Access the latest PHP releases and security updates. Organisations should confirm the appropriate version and follow their hosting provider’s or software vendor’s installation guidance.

PHP Supported Versions

Review which PHP branches remain supported and understand the security implications of operating older, end-of-life versions.

PHP 8 ChangeLog

Review security fixes and release changes to support patch verification and technical assessment.

Additional Security Resources

NCSC Vulnerability Management Guidance

Guidance to help organisations establish effective vulnerability management processes, prioritise remediation and reduce exposure.

NIST National Vulnerability Database

A public vulnerability database providing technical records, severity information and references for published vulnerabilities. Search using CVE-2026-109618 or CVE-2026-109619.

Organisations should continue checking official security advisories as additional technical information becomes available.

Last reviewed: 22 October 2026.

 

This advisory reflects publicly available information as of 22 October 2026. Organisations should consult official vendor guidance for the latest updates and apply remediation appropriate to their environments.

Do You Want Cyber Resilience You Can Trust?

We Deliver Resilience as a Service — Tailored, Transparent, and Aligned to Your Business Outcomes.

Contact Our Team