Critical PHP and NGINX flaws trigger hosting security updates

Saved work

cPanel has issued a security hotfix covering PHP and NGINX, as critical vulnerabilities put affected hosting servers at risk.

cPanel’s November 19 release notes identify EasyApache 4 version 25.98 as a security hotfix. It updates PHP and NGINX, rebuilds NGINX modules and backports PHP security fixes to its PHP 7.4.34 package.

cPanel separately updated its internal PHP packages. Ask which installation was updated, because patching the control panel’s own PHP doesn’t confirm that the PHP serving your website has been patched.

SiteGround said on November 20 that it had patched every PHP version on its shared hosting and cloud servers, including a backport for PHP 7.4. It said the rollout finished at 17:04 UTC on November 19. For sites that also use NGINX, confirm its patch status separately.

The updates reach below WordPress

PHP runs application code for websites built on platforms such as WordPress. NGINX receives web traffic and can serve pages or pass requests to an application. A hosting environment can use both, so updating one component can leave the other needing attention.

The PHP development team released security updates on November 19, 2026. Its advance notice said the critical issues require non-default configurations or uncommon setups. Exposure therefore depends on how the server and application work together.

One critical flaw, CVE-2026-129289, involves PHP-FPM, a service that processes PHP requests. According to PHP’s advisory, an attacker without a login can slip an extra request past the front-end server and run PHP code with the PHP process’s permissions. The attack requires reused backend connections and application code that opens an input stream without fully reading it.

For administrators, relevant settings include NGINX’s fastcgi_keep_conn on and Apache’s enablereuse=on. PHP says configurations that close the FastCGI connection after each request avoid the demonstrated attack. That distinction applies to this flaw; the release contains other security fixes too.

NGINX released its updates on November 18. F5’s advisory for CVE-2026-123007 describes a flaw affecting servers with HTTP/2 enabled. It can crash a worker process or corrupt its memory.

Remote code execution is possible when a memory-protection feature called address space layout randomization is disabled or an attacker can bypass it. F5 rates the flaw critical at 9.2 under CVSS version 4.0.

Wiz Research also documented CVE-2026-123633, a separate HTTP/2 vulnerability fixed in the same NGINX releases. Its researchers demonstrated code execution in lab environments.

Which releases contain the fixes

The PHP and NGINX projects list these fixed releases for existing PHP 8.2 through 8.5 installations and NGINX Open Source.

Software branchRelease containing the fixes
PHP 8.28.2.36
PHP 8.38.3.37
PHP 8.48.4.28
PHP 8.58.5.13
NGINX stable1.30.7
NGINX mainline1.31.9

PHP 8.6.0, released on November 19, also includes the PHP fixes. You can patch an existing supported branch without moving to the newly released PHP 8.6 branch just for this update.

Hosting vendors and operating-system distributors may backport fixes into packages that retain an older base version. Ask for the vendor’s security advisory and full package revision when that happens. NGINX Plus and products built around NGINX follow separate vendor release schedules; their administrators need the applicable product advisory.

PHP 8.1 and earlier no longer receive updates from the PHP project, and PHP 8.2’s security support ends on December 31, 2026. If your website depends on an older branch, ask who supplies its security fixes and arrange an upgrade to a supported branch.

Ask for confirmation from the server owner

On a managed hosting plan, start with your host. On a self-managed server, give the task to the administrator responsible for its operating system and web services. Updating WordPress, themes or plugins doesn’t install these server-level fixes.

Ask for a response covering four points.

  • Affected software. Which PHP versions serve your domains, and does NGINX handle traffic anywhere in the hosting setup?
  • Installed fixes. Which patched releases or vendor package revisions are installed for each affected component?
  • Running services. Have the required service restarts or binary upgrades been completed so the live processes use the patched software?
  • Outstanding work. Are any domains, servers or application instances still waiting, and when will that work finish?

AWS’s PHP bulletin explicitly instructs administrators to restart the services running PHP after updating. A package installation alone can leave long-running processes using the previous code, so the completion check needs to include the running service.

If patching is delayed, have the administrator apply the relevant advisory’s temporary mitigations. For the PHP-FPM request-smuggling flaw, PHP recommends disabling backend connection reuse until the update is installed. That measure addresses a specific attack path and doesn’t replace the remaining security fixes.

After the update, test the functions your business relies on, such as logins, contact forms and checkout. Keep the host’s confirmation with your website maintenance records, including the package details and completion time.

Keep the ticket open until the response confirms which fixes are running in your environment.

Frequently asked questions

Does updating WordPress install the PHP and NGINX security fixes?

No. PHP and NGINX are server components. Your hosting provider or server administrator needs to install the relevant fixes and ensure the running services use the patched software. WordPress, theme and plugin updates are separate maintenance tasks.

Do the PHP and NGINX vulnerabilities affect every website?

No. Exposure depends on the software version, enabled features and application behaviour. The NGINX flaws discussed here require HTTP/2. The PHP-FPM request-smuggling attack requires backend connection reuse and application code that opens an input stream without fully reading it. Your administrator should assess your configuration against the relevant advisories.

Can an older version number still have a security fix?

Yes. A vendor can backport security fixes while retaining an older base version. Ask for the vendor advisory and full package revision confirming the fixes. For an older PHP branch, also confirm who maintains its security updates and plan an upgrade to a supported branch.

Get new small business insights by email

Practical ideas and useful articles to help you make better business decisions.

HelperX Bot

Not sure what to read next?

I can suggest related Tech Help Canada articles based on the topic you’re reading now.

Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us

Leave a Comment

Tweet
Share
Share
Pin
WhatsApp
Reddit
Email