Back to the blog

PHP rolls out critical patches and MySQL fixes 10 flaws

Share

PHP announced a critical update for November 19, while Oracle released 10 fixes for MySQL. There are also new patches for NGINX, Java, and WordPress; the steps depend on the version and the type of hosting.

PHP announced on November 18, 2026, new security updates for all its supported versions, scheduled for Thursday the 19th. A day earlier, Oracle published a bulletin with 10 fixes for the MySQL family, while NGINX, WordPress, and Java also received important advisories during the week.

The difference between these announcements matters: PHP still has an update pending, Oracle has already published its vulnerability matrix, and other projects have patched versions available. For companies running websites, online stores, or administrative systems, the priority is to identify the installed software and apply the corresponding fixes.

PHP prepares a critical update for November 19

The PHP security team confirmed it will release updates on Thursday, November 19, between 14:00 and 14:30 UTC, equivalent to 8:00 and 8:30 a.m. in central Mexico.

The announcement affects all supported PHP branches and notes that the maximum severity of the vulnerabilities is critical. The project itself clarifies that the most serious issues require non-default configurations or unusual environments, so they should not be treated as an identical exposure across all installations.

As of the close of November 18, the version numbers of the new fixed releases and all their technical details had not yet been published.

Which previous flaws remain relevant

On October 21, PHP had fixed two critical remote code execution vulnerabilities:

  • CVE-2026-109618: memory corruption during out-of-memory conditions.
  • CVE-2026-109619: reuse of internal information after memory is freed.

Both could allow unauthenticated code execution. The patches arrived in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12, according to the official advisory.

Later, CVE-2026-115560 was reported, another possible remote code execution issue tied to an unusual combination of session configuration and application code. PHP recommends temporarily disabling upload progress tracking in sessions where applicable, until the final fix is available.

How to protect PHP: confirm that you already have the October patches installed, check whether you use the affected session feature, and prepare for the November 19 update. An experimental version of PHP 8.6 should not be used as a substitute for a production patch.

Oracle releases 10 fixes for MySQL

On November 17, Oracle published its Critical Security Patch Update, with 655 patches distributed across different product families. Ten correspond to the MySQL family and, according to Oracle, three of the vulnerabilities can be exploited remotely without authentication.

The two highest scores correspond to different components:

  • CVE-2026-115557, 9.8/10: affects MySQL Shell and its Python-based client component.
  • CVE-2026-114952, 9.1/10: affects client programs included with MySQL Server and MySQL Cluster, with possible consequences for data confidentiality and integrity.

The 10 vulnerabilities included in the advisory

VulnerabilityComponentCVSS 3.1
CVE-2026-115557MySQL Shell9.8
CVE-2026-114952Client programs9.1
CVE-2026-92392Bundled with cURL8.1
CVE-2026-114951Activity log7.2
CVE-2026-114950Query optimizer7.2
CVE-2026-114949Replication7.2
CVE-2026-127428Geographic functions7.1
CVE-2026-114953Replication6.5
CVE-2026-114122MySQL Workbench3.9
CVE-2026-114948MySQL Cluster2.5

For several of these flaws, Oracle identifies MySQL Server versions 8.4.0 through 8.4.13, 9.7.0 through 9.7.4, and 26.10 as affected. The list varies by component and also includes specific versions of MySQL Cluster.

There is one important caveat: the bulletin's publication does not prove that every patched MySQL Community build is already available. The documentation reviewed still listed later builds as unreleased, so you should check the vendor's downloads and packages before installing.

To patch MySQL, back up your databases, identify the installed branch, and apply the security package available for that distribution. MySQL Shell, Workbench, and the clients used by applications should also be reviewed separately when installed.

NGINX fixes 10 new vulnerabilities

On November 18, NGINX released versions 1.30.7 and 1.31.9, corresponding to its stable and mainline branches. Both include fixes for 10 vulnerabilities related to connection processing, memory, and various server modules.

Among the issues are memory corruption when handling HTTP/2 and an infinite loop when receiving certain requests over TLS 1.3. There are also bugs related to HTTP/3, the mail module, and client certificate validation.

The announced identifiers are CVE-2026-123634, CVE-2026-123007, CVE-2026-121810, CVE-2026-123633, CVE-2026-118899, CVE-2026-113425, CVE-2026-120993, CVE-2026-125283, CVE-2026-120967, and CVE-2026-123640.

How to fix it: update NGINX to 1.30.7 or 1.31.9, depending on the branch you're using, or install the equivalent patched package from your operating system vendor. Then validate your configuration, reload or restart the service, and check HTTPS connections.

WordPress 7.1.5 fixes permission and SQL injection issues

WordPress released version 7.1.5 on November 18 as a security update. It includes fixes for privilege escalation, SQL injection, malicious script execution, and information disclosure.

One of the issues allowed unauthenticated privilege escalation through Template Part block attributes, with possible remote code execution. Another affected multisite installations and could let an administrator gain super admin access.

The update is available from the WordPress dashboard itself, under Dashboard > Updates, as well as from the official downloads. After applying it, it's a good idea to review the plugins, themes, and permissions of the administrative accounts.

These flaws belong to WordPress. Updating the publishing system does not replace the patches needed for PHP or the database.

Java4Shell makes it necessary to review Java servers

Oracle and OpenJDK released fixes on November 17 for CVE-2026-114938, known as Java4Shell. The vulnerability affects Base64 data processing in certain Java installations on x86-64 processors with compatible AVX-512 instructions.

According to CERT-EU, it can cause service disruptions and, under specific conditions, unauthenticated remote code execution. Oracle assigns it 8.1 on CVSS 3.1, and the U.S. agency CISA requested that the patch be applied immediately.

Oracle's bulletin includes 11 fixes for Java SE. Affected systems should use the patched versions that correspond to their distribution, including the Java 17, 21, 25, and 27 branches.

For Java 17, CERT-EU identifies version 17.0.21.1 as patched; for Java 21 it points to 21.0.13.1. It also recommends restarting Java processes after updating, because replacing files without restarting can leave vulnerable components running.

How to apply the patches on servers and hosting

The update should be done component by component, starting with a verifiable backup of the files and databases. The method changes depending on whether you have a directly managed server or a shared hosting service.

ComponentRemediation step
PHPInstall the October patches and the new security releases when they are published on November 19
MySQLCheck the installed edition and apply the available fixed packages according to Oracle's advisory
NGINXUpdate to 1.30.7 or 1.31.9, or use the distributor's equivalent patch
WordPressInstall 7.1.5 from the updates dashboard
JavaUpdate the Java environment to a fixed build and restart its processes

If you use shared hosting with cPanel

In cPanel, you can check the PHP version through MultiPHP Manager or the equivalent manager enabled by your provider. Switching branches and updating security packages are two separate operations: the hosting must offer a build with the corresponding patch.

For MySQL, NGINX, and other server components, the provider usually controls updates. Ask for the exact installed version, the date the November patches were applied, and confirmation that the published vulnerabilities are fixed or do not affect your service.

It's also worth checking whether the hosting uses MariaDB instead of Oracle MySQL. Although the two engines are compatible in many use cases, their security advisories and packages are not interchangeable.

If you manage your own server

With administrative access to WHM, you can check EasyApache 4 for PHP packages and MultiPHP Manager to assign versions to sites. The official cPanel documentation recommends keeping system packages up to date and distinguishes PHP engine updates from the version changes used by each domain.

For MySQL or MariaDB, WHM offers the Upgrade Database Version option, depending on your version. Before modifying the engine, you need to back up the databases and use the compatibility checks; minor security updates can also be distributed through the server's package manager.

After installing the patches, check that the site loads correctly, that user access works, that query and write operations on the database respond, and that no new errors appear in the logs. A backup and a restore test let you recover service if the update causes incompatibilities.

November 19 will be the next review date

PHP has yet to publish its new patched versions. Oracle, NGINX, and WordPress bulletins already make it possible to identify affected components, although package availability depends on the vendor and the hosting provider.

A company may have WordPress up to date and still be running a vulnerable version of PHP or an unpatched MySQL client component. That's why it's necessary to check every installed version and keep evidence of the update, especially when the server is managed by a third party.

Terms in this note

  • CVE: public identifier that makes it possible to locate a specific vulnerability.
  • CVSS: scoring system for classifying the technical severity of vulnerabilities.
  • Remote code execution: the ability to run instructions on another system by exploiting a flaw.
  • Privilege escalation: gaining permissions beyond those an account has.
  • SQL injection: a vulnerability that allows database queries to be altered through manipulated input.
  • NGINX: software that receives and processes web connections and can distribute them to applications.

References

// Category

Cybersecurity

Get site updates

We'll let you know when we publish technology articles, new guides and resources to help you work better.

Only when there is something new on the site. No ads, and you can unsubscribe whenever you like.

Does this look like a challenge at your company?

Tell me how it works today and we'll see whether it makes sense to automate, integrate or improve it.

Tell me your case