Dear Customers and Partners,

On November 18 and 19, 2026, the NGINX project and the PHP development team released patches for a series of security vulnerabilities, including flaws that let an unauthenticated attacker crash the service or execute code remotely (RCE). The same week also brought warnings about Java4Shell in OpenJDK and an actively exploited vulnerability in Apache Axis 1.x.

  • NGINX – CVE-2026-123007: Memory corruption in HTTP/2 flow control, present since version 1.9.5 (2015). An attacker can crash worker processes and, under favorable conditions, execute code. Severity: CVSS 8.1 (v3.1) / 9.2 (v4.0).
  • NGINX – CVE-2026-123633: A use-after-free in HTTP/2 when NGINX acts as a reverse proxy, plus 8 other vulnerabilities (resolver, HTTP/3, mail proxy, PROXY protocol v2, alias with try_files, stream module).
  • Affected NGINX versions: 1.9.5 through 1.31.8 with HTTP/2 enabled. Fixed in 1.30.7 (stable) and 1.31.9 (mainline).
  • PHP – 17 vulnerabilities, 7 rated Critical: most notably CVE-2026-129289 (request smuggling through PHP-FPM), CVE-2026-129496 (use-after-free in the timezone cache) and CVE-2026-126714 (file-based session handling).
  • Affected PHP versions: Branches 8.2 to 8.5 prior to 8.5.13, 8.4.28, 8.3.37 and 8.2.36.
  • Java4Shell (CVE-2026-114938) and Apache Axis 1.x (CVE-2026-90436): A flaw in the OpenJDK Base64 decoder on CPUs with AVX-512 VBMI, and an RCE when Axis 1.x processes a SOAP Fault.

Below are the actions taken and the patching results from the Sudo Engineering Team.

I. FULL INFRASTRUCTURE REVIEW
(Morning of November 20, 2026)

As soon as the alerts were received, Sudo's engineers inventoried every Cloud Server, Hosting system and Kubernetes cluster operated by Sudo:

  • NGINX: All load balancers with HTTP/2 enabled and the entry points (gateway/ingress) of the Kubernetes clusters were marked for immediate patching.
  • PHP: Every server running PHP-FPM, Laravel Octane/FrankenPHP, and every PHP container image needed an update.
  • Java and Apache Axis: Sudo's systems do not use Apache Axis 1.x. The only Java component is an internal CI/CD tool that is not exposed to the Internet and runs on CPUs outside the scope of Java4Shell.

II. UPDATE: PATCH UPGRADES COMPLETED
(Updated at 3:30 PM, November 20, 2026)

After compatibility testing, Sudo rolled out the updates one server at a time, checking the status of every website before and after each step:

ComponentSolutionStatus
NGINX on load balancersApplied the Debian security update (1.22.1-9+deb12u11, with the CVEs above backported)Completed
NGINX Gateway on KubernetesUpgraded to the official NGINX 1.31.9 release, keeping the ModSecurity WAF layerCompleted
Ingress-NGINX on KubernetesDisabled HTTP/2 to remove the attack vector while moving to the new GatewayMitigation applied
PHP 8.5 / 8.4 / 8.2Upgraded to the official patch releases 8.5.13, 8.4.28, 8.2.36Completed
PHP 7.4 / 7.2Applied the backported patches from Sury (7.4.33-37, 7.2.34-70)Completed
Laravel Octane / FrankenPHPUpgraded to FrankenPHP 1.13.6 (PHP 8.5.13 / 8.4.28)Completed
Websites on Kubernetes (containers)Rebuilt the base image with PHP 8.2.36 and redeployed every websiteCompleted

Note: For NGINX, installing the package is not enough; the service must be restarted so that the processes run the new binary. For PHP, long-running processes (queue workers, Octane) must be restarted as well. Sudo completed all of these steps. Downtime on each server was only 1 to 4 seconds, and servers were updated one at a time so that many websites were never affected at once.

Recommendations for customers

  • Websites and servers managed by Sudo: Already patched and running normally. No action is required on your side.
  • Websites running PHP 8.1 or older: These versions are end of life, and PHP 8.2 will stop receiving security fixes on December 31, 2026. Sudo recommends planning an upgrade to PHP 8.3 or later; our engineers are ready to help check source code compatibility.
  • Customers managing their own VPS/Cloud Server:
    • Update NGINX to 1.30.7 / 1.31.9, or to your OS security update (Debian 12: 1.22.1-9+deb12u11, Debian 13: 1.26.3-3+deb13u11), then restart NGINX (a reload is not enough).
    • If you cannot update right away, temporarily disable HTTP/2 by removing the http2 parameter from the listen line or setting http2 off;.
    • Update PHP to 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 (or the Sury backports for 7.x), then restart PHP-FPM, queue workers and Octane. If you use Docker, rebuild your images from the latest php:8.x.y tag.
    • Check your configuration: avoid fastcgi_keep_conn on and catch_workers_output = yes until PHP is patched.
    • Java: update OpenJDK according to your vendor; as a temporary measure, add the -XX:-UseBASE64Intrinsics flag. Apache Axis 1.x: block access to SOAP endpoints and plan a replacement.

More information

Security is a process of continuous monitoring. Sudo will keep watching the situation and update this article as new information becomes available.

Support contacts

Thank you for your trust and cooperation!