• 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 NGINX HTTP/2 - CVE-2026-123633 and CVE-2026-123007

Fede Marsell

Basic Pleskian
Server operating system version
AlmaLinux release 8.10
Plesk version and microupdate number
18.0.81 Update #8
Hi,

Two critical vulnerabilities affecting NGINX HTTP/2 have recently been disclosed: CVE-2026-123633 and CVE-2026-123007, potentially allowing remote code execution.

Is the Plesk team aware of these vulnerabilities, and are there plans to release updated NGINX packages to address them?

In the meantime, would disabling HTTP/2 in NGINX be an effective mitigation until patched packages become available?

If so, is there a recommended way to disable HTTP/2 globally in Plesk without affecting existing websites or having the configuration overwritten?

Thanks,

Fede
 
I disabled http2 until a patch is released and sctp (not needed anyway on my server).
Then added a check for crashes to my server monitoring script. GitHub - cmelius/plesk-monitoring-server-Report: A single bash script for a Plesk server on Linux that writes an hourly health and security report (optionally) uploads it to cloud storage with rclone.

That's not a fix or anything but it tells you when crashes occur.

See changelog.

Disable in plesk.
plesk bin http2_pref --disable
systemctl restart nginx
 
Indeed, plesk bin http2_pref --disable disables HTTP/2 globally in Plesk.

A restart of NGINX afterwards is recommended to ensure the changes are fully applied and no old worker processes remain active.

You can verify this using curl -I --http2 https://yourdomain.com, which should return HTTP/1.1 instead of HTTP/2.
 
Indeed, plesk bin http2_pref --disable disables HTTP/2 globally in Plesk.

A restart of NGINX afterwards is recommended to ensure the changes are fully applied and no old worker processes remain active.

You can verify this using curl -I --http2 https://yourdomain.com, which should return HTTP/1.1 instead of HTTP/2.
But don't forget to disable sctp... It seems that needs to be done also.
 
Quick fix if you have more cfg files:

curl -sk -o /dev/null -w 'HTTP version: %{http_version}\n' --http2 Example Domain

grep -RInE 'http2' /etc/nginx/ --include='*.conf'

tar czf /root/nginx-config-backup-$(date +%Y%m%d-%H%M%S).tar.gz /etc/nginx

ls -lh /root/nginx-config-backup-*.tar.gz

find /etc/nginx -name '*.conf' \( -type f -o -type l \) -print0 |
while IFS= read -r -d '' file; do
target=$(realpath -e "$file") || continue
[ -f "$target" ] || continue

sed -i -E \
-e '/^[[:space:]]*http2[[:space:]]+on[[:space:]]*;/d' \
-e '/^[[:space:]]*listen[[:space:]]/s/[[:space:]]+http2([[:space:];])/ \1/g' \
"$target"
done


nginx -t

systemctl reload nginx

curl -sk -o /dev/null -w 'HTTP version: %{http_version}\n' --http2 Example Domain
HTTP version: 1.1

grep -RInE 'http2' /etc/nginx/ --include='*.conf'
0


# ON YOUR OWN RISK -)

cheers Michael
 
Back
Top