• 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.

Resolved NGINX HTTP/2 - CVE-2026-123633 and CVE-2026-123007

It's pretty disappointing that customers have to help each other deal with such a critical security vulnerability while there's barely any communication from Plesk and we're still waiting for a patch. ...
That fix came out yesterday. It'll need to be tested, then packaged into an update, than published to Plesk users. Give developers that time, from while to while they need to sleep at night, too. I agree with your position though, if this isn't done today.
 
I strongly disagree. First of all, the Plesk article mentioned above should have been posted here by a Plesk employee, not discovered and shared by a customer. I work in the software industry myself, and when a critical security vulnerability potentially affects tens of thousands of servers, responding urgently is part of the job, even if that means working overtime. This isn't just another routine update. And at the very least, customers deserve proactive communication from Plesk.
 
Plesk just doesn’t care anymore. Some months ago, they started sending emails when critical issues had been fixed and a patch release was coming soon - tomorrow, for example. That was a good idea, but they stopped sending these important informational emails for no apparent reason and without any explanation.

There is also still a lack of information about Plesk’s own bugs. We get notes like “More details to follow shortly” in the changelog, but no further details are published - famous last words. It’s a black box, and we have no way of knowing whether our clients were affected or whether we need to inform the authorities about data breaches, NIS2 incidents, etc.
 

Anyone else getting multiple outputs of:

Code:
PHP Warning: Array to string conversion; File: /usr/local/psa/admin/plib/api-rpc/ExpandXMLLib.php, Line: 214

PHP Warning:  Array to string conversion in /usr/local/psa/admin/plib/api-rpc/ExpandXMLLib.php on line 214

And one of my servers also included this error a couple of times:

Code:
ERR [panel] strtolower(): Argument #1 ($string) must be of type string, array given

When using the mitigation step of:

Code:
plesk bin http2_pref --disable

From: https://support.plesk.com/hc/en-us/...ecution-in-NGINX-shipped-with-Plesk-for-Linux

The final output is, in all cases:

Code:
HTTP/2 support was successfully deactivated.

And I checked one of my domains, and it reported

Code:
ALPN protocol: http/1.1
 
@bernes_stainz idea is great, because it circumvents the enormous risk gap of a webserver reconfiguration process run by Plesk on servers with many domains. But the script does not catch many confs, and it has no backup if something fails. I suggest a different solution:

Code:
#!/usr/bin/env python3
"""Temporarily change HTTP/2 in Nginx's included Plesk configuration files."""

import argparse
import difflib
import os
import re
import subprocess
import sys
import tempfile
from pathlib import Path


CONFIG_FILE = re.compile(rb"(?m)^# configuration file (.+):$")
HTTP2_ON = re.compile(rb"(?m)^([ \t]*http2[ \t]+)on(?=[ \t]*;)")
HTTP2_OFF = re.compile(rb"(?m)^([ \t]*http2[ \t]+)off(?=[ \t]*;)")
LISTEN = re.compile(rb"(?m)^[ \t]*listen[ \t]+[^#;\r\n]+;")
LEGACY_HTTP2 = re.compile(rb"[ \t]+http2(?=[ \t;])")
LEGACY_MARKER = b" # plesk-nginx-http2: restore listen http2"
DISABLED_LISTEN = re.compile(
    rb"(?m)^([ \t]*listen[ \t]+[^#;\r\n]+);"
    + re.escape(LEGACY_MARKER)
    + rb"(?=[ \t\r\n#]|$)"
)


def included_files():
    dump = subprocess.check_output(["nginx", "-T"])
    paths = {Path(os.fsdecode(name)).resolve(strict=True)
             for name in CONFIG_FILE.findall(dump)}
    if not paths:
        raise ValueError("Could not identify included files in nginx -T output.")
    return paths


def disable_http2(config, mark_legacy=True):
    def disable_listen(match):
        directive = match[0]
        disabled = LEGACY_HTTP2.sub(b"", directive)
        return disabled + LEGACY_MARKER if mark_legacy and disabled != directive else disabled

    config = HTTP2_ON.sub(rb"\g<1>off", config)
    return LISTEN.sub(disable_listen, config)


def enable_http2(path, current, backup):
    if backup is None:
        enabled = HTTP2_OFF.sub(rb"\g<1>on", current)
        return DISABLED_LISTEN.sub(rb"\g<1> http2;", enabled)

    saved = backup / path.relative_to("/")
    if not saved.is_file():
        return current

    original = saved.read_bytes()
    if current == original:
        return current
    if current not in (disable_http2(original), disable_http2(original, mark_legacy=False)):
        raise ValueError(
            f"{path} differs from the disabled version of {saved}. "
            "Compare the two files and restore the HTTP/2 directives manually "
            "to preserve other changes."
        )
    return original


def show_changes(changes):
    for path, before, after in changes:
        name = os.fsencode(path)
        diff = difflib.diff_bytes(
            difflib.unified_diff,
            before.splitlines(keepends=True),
            after.splitlines(keepends=True),
            fromfile=name + b" (current)",
            tofile=name + b" (proposed)",
            n=0,
        )
        for line in diff:
            sys.stdout.buffer.write(line if line.endswith(b"\n") else line + b"\n")
    sys.stdout.buffer.flush()
    print(f"Staging: {len(changes)} file(s) would change.")


def apply_changes(changes):
    backup = Path(tempfile.mkdtemp(prefix="nginx-http2-", dir="/root"))
    for path, before, _ in changes:
        saved = backup / path.relative_to("/")
        saved.parent.mkdir(parents=True, exist_ok=True)
        saved.write_bytes(before)

    print(f"Backup of {len(changes)} file(s): {backup}", flush=True)
    attempted = []
    try:
        for path, before, after in changes:
            if path.resolve(strict=True) != path or path.read_bytes() != before:
                raise ValueError(f"{path} changed during the run.")
            # Modify the resolved file in place to preserve its metadata and aliases.
            attempted.append((path, before, after))
            path.write_bytes(after)
        subprocess.run(["nginx", "-t"], check=True)
    except (OSError, ValueError, subprocess.CalledProcessError, KeyboardInterrupt):
        for path, before, after in reversed(attempted):
            try:
                current = path.read_bytes()
                # A failed write may leave a prefix of the intended contents.
                if path.resolve(strict=True) != path or not after.startswith(current):
                    print(f"{path} changed during rollback. See {backup}.", file=sys.stderr)
                else:
                    path.write_bytes(before)
            except OSError as error:
                print(f"Could not restore {path}: {error}. See {backup}.", file=sys.stderr)
        raise


def main():
    parser = argparse.ArgumentParser(description=__doc__)
    modes = parser.add_subparsers(dest="mode")
    disable = modes.add_parser("disable", help="Disable HTTP/2 in included files")
    enable = modes.add_parser("enable", help="Enable HTTP/2 in included files")
    enable.add_argument("--from-backup", type=Path, metavar="DIRECTORY",
                        help="Restore the original HTTP/2 settings from a disable run")
    for mode in (disable, enable):
        mode.add_argument("--dry-run", "--stage", action="store_true",
                          help="Show the diff without editing files or restarting Nginx")
    args = parser.parse_args()
    if args.mode is None:
        parser.error("Choose disable or enable.")

    backup = args.from_backup if args.mode == "enable" else None
    if backup is not None and not backup.is_dir():
        parser.error(f"Backup directory does not exist: {backup}")

    changes = []
    for path in sorted(included_files()):
        before = path.read_bytes()
        after = (disable_http2(before) if args.mode == "disable"
                 else enable_http2(path, before, backup))
        if before != after:
            changes.append((path, before, after))

    if args.dry_run:
        show_changes(changes)
    elif changes:
        apply_changes(changes)
        try:
            subprocess.run(["systemctl", "restart", "nginx"], check=True)
        except (OSError, subprocess.CalledProcessError):
            print("The validated configuration is on disk, but Nginx restart failed.",
                  file=sys.stderr)
            raise
    else:
        print("No files need changing.")


if __name__ == "__main__":
    try:
        main()
    except (OSError, ValueError, subprocess.CalledProcessError) as error:
        sys.exit(str(error))
    except KeyboardInterrupt:
        sys.exit(130)

Code:
Usage:
# Preview either change
python3 plesk-nginx-http2.py disable --stage
python3 plesk-nginx-http2.py enable --stage

# Apply either change
python3 plesk-nginx-http2.py disable
python3 plesk-nginx-http2.py enable

The script does not only cover the /var/www/system/<domain>/conf nginx.conf files, but also the webmail configurations and possible "additional Nginx directives" where a http2=on could reside. It also backups the files before it changes them to /root/nginx-http2-<random> and is able to
a) turn http/2 back on using the current .conf file or
b) turn http/2 back on by restoring the file from a previous backup. For the later use
python3 plesk-nginx-http2.py enable --from-backup /root/nginx-http2-XXXXXXXX [--stage]

I grant no warranty whatsoever. Use at your own risk. But I can tell you that it was successfully used in production on many dedicated servers on Alma 8, 9, 10 with a medium 5-digit-number of domain configuration files.

Downside: This does not change the Plesk database, so if a user applys changes to his hosting configuration, Plesk will overwrite the "quick change" done by the script.

Thanks @Bitpalast and @bernes_stainz !

@Bitpalast When decided to use your python script, should I still execute
Bash:
plesk bin http2_pref --disable
to prevent a configuration change in GUI to re-enable http2 on domain ?
If so should I execute it before or after your script ?
 
Thanks @Bitpalast and @bernes_stainz !

@Bitpalast When decided to use your python script, should I still execute
Bash:
plesk bin http2_pref --disable
to prevent a configuration change in GUI to re-enable http2 on domain ?
If so should I execute it before or after your script ?
Running the Plesk command will reconfigure the Plesk psa database and all webserver configuration files. It is the more robust approach, but on servers with many domains, this will likely first remove all .conf file symbolic links from the /etc/nginx and /etc/httpd directories, then regenerate them slowly so that for a long while, e.g. 10, 20, 30, 40 minutes or so (depending on the number of files), websites will stop working should the webserver reload or restart in that window. That's why others and me suggested to directly edit the conf files instead.

I you use my script, currently there is no urgent need to also use the Plesk command. Only if users update their webhosting settings themselves afterwards, their domain settings will revert to http/2 if the Plesk command was not run, but that is statically neglectible, very, very low remaining risk.
 
Thanks @Bitpalast and @bernes_stainz !

@Bitpalast When decided to use your python script, should I still execute
Bash:
plesk bin http2_pref --disable
to prevent a configuration change in GUI to re-enable http2 on domain ?
If so should I execute it before or after your script ?
Running the Plesk command will reconfigure the Plesk psa database and all webserver configuration files. It is the more robust approach, but on servers with many domains, this will likely first remove all .conf file symbolic links from the /etc/nginx and /etc/httpd directories, then regenerate them slowly so that for a long while, e.g. 10, 20, 30, 40 minutes or so (depending on the number of files), websites will stop working should the webserver reload or restart in that window. That's why others and me suggested to directly edit the conf files instead.

I you use my script, currently there is no urgent need to also use the Plesk command. Only if users update their webhosting settings themselves afterwards, their domain settings will revert to http/2 if the Plesk command was not run, but that is statically neglectible, very, very low remaining risk.
running a cronjob every 15 minutes with the python script will lower it down to zero -)

cheers Michael
 
There are updates that are being applied when running but not clear if this addresses the php updates or just nginx


plesk installer --select-release-latest --upgrade-installed-components
 
The update has arrived.

Plesk installs 2 nginx servers as far as i know: 1 for the plesk panel itself and 1 as proxy before apache httpd

The public facing one has now been updates to 1.30.7

Any one knows how to test the version on the Plesk own webserver?
 
It's unclear if the updates are hitting php versions, the plesk packaged nginx, and the internal plesk nginx so that we can re-enable http/2
 
disabling http/2 was never a solution. It mitigated 2 of the 5 issues. (2 of the 4 if you don't use http/3)


CVEAffected configurationFirst affected release for this pathBlocked by disabling HTTP/2?
CVE-2026-123007HTTP/2 enabled1.9.5Yes
CVE-2026-123634resolver, a request-derived proxy_pass destination, and mirror with mirror_request_body off1.13.4No
CVE-2026-123633HTTP/2 with requests forwarded to an upstream (backend) server1.19.7Yes
CVE-2026-121810HTTP/3 with requests forwarded to an upstream (backend) server1.25.0No
CVE-2026-113425Mail proxy using proxy on and auth_http0.5.15No
 
As far as I can see, the updates that have just become available include the critical PHP security fixes as well as nginx 1.30.7 for both hosted websites and the Plesk panel itself.

The installed nginx versions can be checked using /usr/sbin/sw-cp-serverd -v for the Plesk panel and /usr/sbin/nginx -v for hosted websites.
 
Back
Top