• 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)?

I understand we may not know yet but, will disabling hosting on affected domains (below patched PHP versions) be enough to temporarily mitigate the exploit?
 
Some news from plesk :
Vulnerability CVE-2026-109618 and CVE-2026-109619: Remote code execution in PHP shipped with Plesk

A fix is in development. The PHP vendor has scheduled the release of fixed PHP versions for 21 October 2026 at 14:00 UTC (PHP News Archive | 20 Oct 2026). After that, Plesk will rebuild the following and deliver them to Plesk servers:

PHP builds from Plesk: 7.4 (EOL), 8.0 (EOL), 8.1 (EOL), 8.2, 8.3, 8.4, 8.5
Plesk Obsidian 18.0.80 and 18.0.81 will receive a fix for sw-engine (PHP engine used by Plesk itself)
You mean that Plesk will be able to provide patches for PHP 7.4 (EOL), 8.0 (EOL), 8.1 (EOL)?

If yes, this are excellent news.
 
Just now: RELEASED!

sorry, that was an old article ... look at the start page!
 
is plesk important enough to be included in:
"Linux distributions and LTS vendors received the patches in advance, so check your vendor for updated packages."
 
Apt Update Bookworm. This is not helping

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP82_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP83_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP84_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
 
I think Plesk update is down
Error: Unable to receive update information for the package(s)

With an apt-update (Debian), I get:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP82_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP83_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP84_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP85_17 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: Failed to fetch http://autoinstall.plesk.com/PHP82_17/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: Failed to fetch http://autoinstall.plesk.com/PHP83_17/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: Failed to fetch http://autoinstall.plesk.com/PHP84_17/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: Failed to fetch http://autoinstall.plesk.com/PHP85_17/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5B6AB2160B50DB96
W: Some index files failed to download. They have been ignored, or old ones used instead.
 
Thank you plesk for the fast reaction - all servers are updated (through the interface, apt-get had some issues)
 
How long wil this update take? It seems to be hanging here as well.
 

Attachments

  • Screenshot_20261021_160812_Chrome.jpg
    Screenshot_20261021_160812_Chrome.jpg
    332.6 KB · Views: 9
I have upgraded Plesk's managed PHP versions but it seems that the Admin Panel's PHP has not been updated? Any ideas?

# /usr/local/psa/admin/bin/php -v
PHP 8.4.24 (cli) (built: Aug 27 2026 07:14:20) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.4.24, Copyright (c) Zend Technologies
with Zend OPcache v8.4.24, Copyright (c), by Zend Technologies
 
Back
Top