Articles in this section

Critical PHP Security Release on 19 Nov 2026

kb: technical kb: security

Situation

The PHP security team announced security releases scheduled for Thursday, 19 November 2026, between 14:00 and 14:30 UTC . They address security vulnerabilities affecting all supported PHP versions. The highest severity is CRITICAL. The fixed vulnerabilities and their CVE IDs are listed in the PHP changelog for each version.

Affected product versions

Check the installed Plesk version as described in How to find version of Plesk installed on server? .

All supported PHP versions are affected. Plesk updates with the fixed PHP versions have been released.

Product / Component Affected versions Patched versions Status
Plesk for Linux, PHP engine of the panel ( sw-engine )
  • Plesk Obsidian 18.0.81 through 18.0.81 Update 8
  • Plesk Obsidian 18.0.82 through 18.0.82 Update 3
  • Plesk Obsidian 18.0.81 Update 9
  • Plesk Obsidian 18.0.82 Update 4
Patched
Plesk for Windows, PHP engine of the panel ( plesk-engine )
  • Plesk Obsidian 18.0.81 through 18.0.81 Update 8
  • Plesk Obsidian 18.0.82 through 18.0.82 Update 3
  • Plesk Obsidian 18.0.81 Update 9
  • Plesk Obsidian 18.0.82 Update 4
Patched
PHP 8.5 for client websites, Plesk for Linux and Windows   8.5.13 Patched
PHP 8.4 for client websites, Plesk for Linux and Windows   8.4.28 Patched
PHP 8.3 for client websites, Plesk for Linux and Windows   8.3.37 Patched
PHP 8.2 for client websites, Plesk for Linux and Windows   8.2.36 Patched
PHP 8.1 (EOL) for client websites, Plesk for Linux   8.1.34 (security fixes from PHP 8.2.36 backported) Patched
PHP 8.0 (EOL) for client websites, Plesk for Linux   8.0.30 (security fixes from PHP 8.2.36 backported) Patched
PHP 7.4 (EOL) for client websites, Plesk for Linux   7.4.33 (security fixes from PHP 8.2.36 backported) Patched

The PHP project does not specify the affected versions for each vulnerability, and the list of fixed vulnerabilities differs between PHP versions. See the PHP changelog for the fixes included in each version.

Note: for older versions of PHP (5.6, 7.2, 7.3) it is recommended to use paid TuxCare Extended Lifecycle Support for PHP .

For the release timelines of CloudLinux alt-PHP and ELS OS PHP packages, see the CloudLinux status page: PHP security releases, November 19 2026 (Critical) .

Call to action

  1. Update Plesk and PHP to the patched versions listed above.
  2. When the updates are released, install them as described in How to install Plesk updates .

Release notes for the updates will be published in the Change Log for Plesk Obsidian .

Both Plesk updates (18.0.81 Update 9 and 18.0.82 Update 4) also include NGINX 1.30.7 (CVE-2026-123007). For details, see NGINX2Root: Remote code execution in NGINX shipped with Plesk for Linux .

How to make sure the server is protected

Check the installed Plesk version as described in How to find version of Plesk installed on server? and make sure it matches or is newer than the version in the Patched versions column above.

Impact

The PHP security team rates the highest severity of these vulnerabilities as CRITICAL. Servers running unpatched PHP versions may be exposed. This article will be updated when more information is available.

Additional Information:

If the update fails with The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96 error (on Ubuntu/Debian), check the Unable to update Plesk: The following signatures couldn't be verified because the public key is not available article.

How to check PHP version on Plesk server:

In Plesk UI:
  1. Log into Plesk .
  2. Navigate to Tools & Settings > PHP Settings menu. Versions should be reflected in handler names:

Plesk-php-handlers.png

In CLI (Linux):
  1. Connect to the server via SSH
  2. Execute the command below for the corresponding PHP version (8.3 is used in this example). The first line of the output shows the PHP version and the build date:

    # /opt/plesk/php/8.3/bin/php -v

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.