• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question ETA for critical PHP security updates (CVE-2026-109618 / CVE-2026-109619)?

The PHP 7.4 and 8.0 versions are no longer available in the component selection. They are still installed on the server, but the updater doesn't pick up any updates. Does anybody know what could be wrong?
 

Attachments

  • Scherm­afbeelding 2026-10-21 om 20.52.35.png
    Scherm­afbeelding 2026-10-21 om 20.52.35.png
    63.6 KB · Views: 8
Hello,
if anyone is not receiving updates and is hosting with STRATO, change the mirror URLs in plesk.list from the STRATO mirrors to autoinstall.plesk.com.
 
Yes, Plesk packages a seperate version of PHP for use with its own services. To date these have not been updated so while websites running on an updated Plesk server are no longer vulnerable, Plesk effectively still is until the version is updated.

If you run this and it comes back with PHP 8.4.25, then the Plesk panel itself becomes the attack vector:

/usr/local/psa/admin/bin/php -v

A release to address this as soon as possible would help to close that gap.
 
When will updates 18.0.80#11 and 18.0.81#4 finally be released? It can't be right that the most important update is still pending! Other panels have had this sorted out for a long time now; with just the PHP updates, only the customers' websites are secure—the main interface isn't yet!
 
Easy update; Go to Tools & Settings->Updates->Update Components.

To force Node.js updates and fix the vulnerabilities released today October 21:

plesk php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/nodejs/scripts/nodejs-auto-update.php'

No updates will be released for PHP 8.1 or older.
No updates for end-of-life Node.js versions 27.3.1 or older
 
Hello, I used the GUI update in Tools & Settings > Updates, it brought down the new patch versions for PHP 8 with changed version numbers, and also patches for 7.4.33, I understand that its version number does not change, but can you confirm, am I looking at the patched version? It would be super helpful if that article actually showed the build numbers, if possible..?

plesk-php74 7.4.33-1centos.7.261021.1344 (PLESK_17_PHP74)
 
Why can DirectAdmin update/patch everything within 3 hours, where Plesk takes many more hours???

Even DirectAdmin even patched PHP versions from 5.4 to 8.5! Without the use of expensive third-party TuxCare solutions.
Great service from DA to be honest!
 
Hello, I used the GUI update in Tools & Settings > Updates, it brought down the new patch versions for PHP 8 with changed version numbers, and also patches for 7.4.33, I understand that its version number does not change, but can you confirm, am I looking at the patched version? It would be super helpful if that article actually showed the build numbers, if possible..?

plesk-php74 7.4.33-1centos.7.261021.1344 (PLESK_17_PHP74)
I think I answered my own question, I used the CLI route to check the build date:

Code:
# /opt/plesk/php/7.4/bin/php -v
PHP 7.4.33 (cli) (built: Oct 21 2026 13:52:02) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with the ionCube PHP Loader + ionCube24 v14.4.0, Copyright (c) 2002-2025, by ionCube Ltd.
    with Zend OPcache v7.4.33, Copyright (c), by Zend Technologies
 
Back
Top