Articles in this section

Vulnerability CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425 (NGINX2Root): Remote code execution in NGINX shipped with Plesk for Linux

kb: security kb: ai-created kb: ai-edited

Situation

Five security vulnerabilities, also known as NGINX2Root, were discovered in NGINX. Plesk for Linux ships NGINX as the web server for websites (sw-nginx) and as the web server of the Plesk interface (sw-cp-server). These security vulnerabilities have been identified as CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425.

Affected product version

Product / Component Affected versions Patched versions
Plesk for Linux: NGINX for websites (sw-nginx)
  • NGINX 1.30.6 and earlier
  • Plesk Obsidian 18.0.82 Update 3 and earlier
  • Plesk Obsidian 18.0.81 Update 8 and earlier
  • NGINX 1.30.7
  • TBA Plesk release
Plesk for Linux: Plesk interface (sw-cp-server)
  • NGINX 1.30.6 and earlier
  • Plesk Obsidian 18.0.82 Update 3 and earlier
  • Plesk Obsidian 18.0.81 Update 8 and earlier
  • NGINX 1.30.7
  • TBA Plesk release

Impact

A remote attacker who does not need to log in can crash NGINX or run their own code on the server (remote code execution, RCE). Only servers where NGINX uses HTTP/2, HTTP/3, the resolver or mirror directives, or the NGINX mail proxy are exposed.

Call to action

The Plesk development team is preparing an update with NGINX 1.30.7, which fixes all five vulnerabilities.

In the meantime, apply the mitigation below to reduce the exposure of the server.

Follow this article or the Plesk Obsidian change log for updates on the release.

Mitigation

The mitigation turns off the NGINX features that the vulnerabilities need on websites served by NGINX.

Warning: The following steps will cause a brief service interruption.

  1. Connect to the server via SSH.
  2. Disable HTTP/2 for all websites. Websites keep working over HTTP/1.1, but may load slightly slower:

    # plesk bin http2_pref --disable

  3. Verify that NGINX no longer negotiates HTTP/2:

    Note: Replace 203.0.113.2 with the server's IP address and example.com with a website hosted on the server.

    # openssl s_client -connect 203.0.113.2:443 -servername example.com -alpn h2,http/1.1 </dev/null

    The output must not contain ALPN protocol: h2.

Note: The steps above do not change custom configuration. If http2 on;, http3 on;, a listen directive with the http2 or quic parameter, resolver or mirror is used in the Additional nginx directives of a website (Domains > example.com > Apache & nginx Settings) or in a custom configuration template (/usr/local/psa/admin/conf/templates/custom/, see How to modify domain's configurations in Plesk permanently), remove it there as well.

After the Plesk update with the fix is installed, enable HTTP/2 again and restore any directives removed:

# plesk bin http2_pref --enable

Fix tracking: PPP-74036, PPP-74035, PPP-74032.

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.