• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Critical PHP Security Release [18/11/2026]

Franchino

New Pleskian
Server operating system version
Almalinux 9.9
Plesk version and microupdate number
18.0.82 #3
The PHP security team announces upcoming security releases scheduled for Thursday, 19 November 2026, between 14:00 and 14:30 UTC.

These releases are part of PHP’s regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions. The highest severity is CRITICAL.

The issues rated CRITICAL require either non-default configuration or uncommon setups.

Users are strongly encouraged to prepare to upgrade promptly once the releases become available. Technical details and fixed version numbers will be published alongside the releases.

Thank you for helping us keep PHP secure.
 
It would be great to have a faster release cycle for this upcoming PHP patch compared to the last one two weeks ago.
 
Hi, everyone. Our engineers are working on the updates to be released soon after PHP publishes their official builds.
  • Panel PHP engine updates for: Plesk 18.0.81.9 and 18.0.82.4
  • PHP for client websites:
Linux and Windows:
  • Updated PHP 8.5 to version 8.5.13.
  • Updated PHP 8.4 to version 8.4.28.
  • Updated PHP 8.3 to version 8.3.37.
  • Updated PHP 8.2 to version 8.2.36.

Linux only:
  • Backported the security fixes from PHP 8.2.36 to PHP 8.1.34, 8.0.30, and 7.4.33 (EOL).
 
@Sebahat.hadzhi

Hi, for older websites we're using TuxCare Extended Lifecycle Support for PHP.

Will the updates for this also be available at the same time as the PHP updates from Plesk, or possibly even earlier??
 
The ETA for the PHP updates is today around 2 PM (UTC).

@TorbHo , yes, CloudLinux are already working on the ELS PHP versions. You can follow their status page here. If something is unclear, please let me know, so I can raise the question with them internally.
 
I typed

plesk daily CheckForUpdates
plesk bin product_info -u

and

dnf clean expire-cache
dnf check-update

in SSH console, and now updates are available,

Only clicking in plesk wasn't showing updates
 
Just a heads up, the PHP updates seem to introduce a breaking change. I haven't found any PHP release notes at the time of writing this post, so I can't say for sure. But I encountered couple of websites that have gone down with a 500 "Session ini settings cannot be changed at runtime when session.upload_progress.enabled" error. From what I gathered so far, the "Really Simple SSL" Wordpress plugin configures ini settings at runtime for sessions, which (can) cause problems. Obviously this affects other frameworks or CMSes with similar runtime configuration as well.
 
Last edited:
Just a heads up, the PHP updates seem to introduce a breaking change. I haven't found any PHP release notes at the time of writing this post, so I can't say for sure. But I encountered couple of websites that have gone down with a 500 "Session ini settings cannot be changed at runtime when session.upload_progress.enabled" error. From what I gathered so far, the "Really Simple SSL" Wordpress plugin configures ini settings at runtime for sessions, which (can) cause problems. Obviously this affects other frameworks or CMSes with similar runtime configuration as well.
Security hardening: Following session serializer vulnerabilities (including PHP2Shell / CVE-2026-109618, CVE-2026-109619, and CVE-2026-115560), PHP rejects runtime ini_set() changes to session settings when upload progress tracking is enabled. (see CVE-2026-115560: Unpatched PHP RCE Vulnerability why it was done.)

Application/plugin conflicts: Plugins, themes, or frameworks that call ini_set() on session settings at runtime—such as WordPress plugins that modify session configuration on the fly—can trigger this error if session.upload_progress.enabled is explicitly turned on.

Mitigation (more or less ...)
Leave session.upload_progress.enabled disabled: The patch disables upload progress by default. Unless your application explicitly needs session-based upload progress bars, remove any explicit session.upload_progress.enabled = 1 / On overrides.
Audit runtime ini_set() session calls: Check your application code, plugins, and frameworks for runtime calls changing session.* directives (especially session.serialize_handler) and configure them statically in php.ini or your PHP-FPM pool instead.
Explicitly enable only when needed: If an application genuinely requires upload progress and does not conflixt with runtime session changes, set session.upload_progress.enabled = 1 in your server or pool configuration and restart PHP/web workers.
 
Back
Top