nginx, PHP and Java: the November 2026 Security Updates and What to Install

    November 23, 2026

    Security Notes.

    On 18 and 19 November nginx and PHP both published security releases, the same week as an out-of-band fix for Java. A typical Magento store runs all three: nginx in front, PHP-FPM behind it, and Java inside OpenSearch or Elasticsearch, which power catalogue search. Here is what changed and what to install.

    nginx 1.30.7 and 1.31.9

    On 18 November nginx released 1.30.7 (stable) and 1.31.9 (mainline). Together they fix ten vulnerabilities, most of them in code that nearly every installation uses. nginx rates three of them as major:

    • CVE-2026-123007: memory corruption in HTTP/2 flow control. It affects every version since 1.9.5, the first with HTTP/2.
    • CVE-2026-118899: an infinite loop while reading a client request body over TLS 1.3, in every version since 1.13.0.
    • CVE-2026-113425: a use-after-free in the mail proxy module.

    The rest include use-after-free bugs in HTTP/2 (CVE-2026-123633), HTTP/3 (CVE-2026-121810) and the resolver (CVE-2026-123634), an SNI bypass for client certificate checks in the stream module (CVE-2026-120967), and a buffer overflow when alias is combined with try_files (CVE-2026-125283). It is the latest of several nginx security releases this year: the nginx advisories page already lists 36 CVEs from 2026.

    What to install: 1.30.7 or 1.31.9. If you use your Linux distribution's nginx package, look for these CVE IDs in its changelog: distributions often backport fixes and keep the old version number.

    PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36

    A month after the critical October fixes, PHP released another set of security updates on 19 November: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The 8.5.13 changelog lists 18 CVEs; older branches get most of them. The ones that matter most on a web server:

    • PHP-FPM: request smuggling through an unread request body (CVE-2026-129289), a use-after-free in the event loop that can lead to local privilege escalation (CVE-2026-129291), and XSS on the FPM status page (CVE-2026-129292).
    • Sessions: a session serializer mismatch (CVE-2026-115560, the issue PHP warned about on 23 October) and partially overwritten session files (CVE-2026-126714), both of which can lead to remote code execution, plus a use-after-free after an interrupted session shutdown (CVE-2026-129481).
    • Engine: a use-after-free in the timezone cache that can lead to remote code execution (CVE-2026-129496).
    • Other: a PHAR signature bypass through an algorithm downgrade (CVE-2026-128090), and mixed-case HTTPS:// and FTPS:// URLs that could expose data in plain text (CVE-2026-128064).

    PHP 8.6.0 came out the same day and includes these fixes. Keep the support calendar in mind: PHP 8.2 stops receiving security fixes on 31 December 2026, and 8.4 moves to security-only updates on the same date.

    What to install: the latest release of your branch. If you still rely on PHP 8.2, plan the upgrade now.

    Java: the October update and two follow-ups

    Oracle's quarterly Critical Patch Update was scheduled for 20 October 2026. The matching builds are Java 8u511 from Oracle and Eclipse Temurin 17.0.21, 21.0.13, 25.0.5 and 27.0.1. Two follow-ups came after it:

    • eMudhra certificates (CVE-2026-91403 and CVE-2026-114820). Oracle published two security alerts and new builds that distrust certificates linked to the certificate authority eMudhra. The second one removes the roots behind them from the JDK trust store; in Temurin these are AAA Certificate Services and emSign ECC Root CA - G3. Temurin shipped the change on 27 October.
    • CVE-2026-114938 (18 November). A memory corruption bug in OpenJDK 17 and later lets an unauthenticated remote attacker run code on x64 machines whose CPUs support AVX-512 VBMI. Java 8 and 11 are not affected. It is fixed in Temurin 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Until you can update, the advisory's workaround is to start Java with -XX:-UseBASE64Intrinsics.

    Removing a root certificate can break outgoing HTTPS calls to services that still chain up to it, so after updating, test the integrations your applications call from Java. The next scheduled Java update is on 19 January 2027.

    For Magento stores: OpenSearch and Elasticsearch ship with their own bundled JDK, so updating the system Java does not update them. Update the search engine itself, or point it at a patched JDK.

    A short checklist

    • Run nginx -v on every web server and load balancer. You need 1.30.7 or 1.31.9, or a distribution package with the fixes.
    • Check the PHP version your web workers actually run, not only the command line: php-fpm -v for each pool's binary, or phpinfo() behind a restricted URL.
    • Run java -version for every Java runtime, including the ones bundled with search engines and other tools.
    • Restart the services after updating: a patched package changes nothing until the old processes are gone.

    If you'd like a second pair of eyes on your stack, or want us to handle updates like these for you, get in touch. Keeping stores safe and running is a big part of what we do every day.