Skip to main content

PHP Vulnerabilities, November 2026: 7 Critical Flaws and Fixes

  • Published
  • 11 min read
Cover image: PHP Vulnerabilities, November 2026: 7 Critical Flaws and Fixes
Contents10

On 19 November 2026, the PHP development team released the security releases PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, which fix 17 vulnerabilities. Seven of them are rated "Critical", and under certain conditions they may let someone run programs on your server from outside (remote code execution). These are different vulnerabilities from "PHP2Shell", which made the news in October, so servers that were updated to the October fixed releases need to be updated once more.

IPA (Information-technology Promotion Agency, Japan) issued an alert on 20 November, and on the same day JPCERT/CC also updated its PHP2Shell alert. This article is for companies whose websites or business systems run on PHP. It explains the affected versions, the main vulnerabilities and their conditions, settings for when you can't update right away, and what to ask your development company to do.

Key takeaways

  • If you use PHP, update to 8.5.13, 8.4.28, 8.3.37, 8.2.36 or later. The October fixed releases (8.5.12 and so on) do not fix these issues.
  • Many of the seven Critical issues can be exploited only with particular settings or ways of use. However, some involve standard PHP features (such as sessions saved to files), so you cannot say for certain that "it's safe because it uses the default settings".
  • As of 21 November 2026, we have not found official information that these vulnerabilities have been used in actual attacks.
  • Security support for PHP 8.2 ends on 31 December 2026. No fixed releases will be provided for PHP 8.1 or earlier.

17

Vulnerabilities fixed in the 19 November releases

7

Of those, rated Critical (by the PHP development team)

None confirmed

Actual exploitation (as of 21 November, official information)

Terms used here

PHP-FPM = the mechanism that lets a web server such as nginx or Apache call and run PHP programs. It is used on many servers.

Session = the mechanism that remembers things like being logged in as you move from page to page. By default, PHP saves sessions to files on the server.

Gadget chain = an attack technique in which the attacker links together pieces of program code that already exist in an app or library and misuses them.

KEV = a list published by the US CISA of "vulnerabilities confirmed to have actually been exploited".

What happened (November 2026)

  • PHP announced the upcoming releases. It gave advance notice that "the highest severity is Critical, but non-default settings or less common configurations are required". IPA also called on 19 November for people to get ready.
  • Fixed releases published. PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fixed 17 issues. On the same day, PHP 8.6.0, a new release series, was also published.
  • Alerts from IPA and JPCERT/CC. JPCERT/CC says that some of the vulnerabilities also affect features used with the default settings, and that researchers have demonstrated methods leading to arbitrary code execution, while no information has been confirmed showing that they have been exploited in actual attacks.
  • Not yet in KEV. The 17 issues are not in CISA's KEV (20 November edition).

Affected versions and where to move

Current PHPAffectedMove toEnd of security support
PHP 8.58.5.12 and earlier8.5.13 or later31 December 2029
PHP 8.48.4.27 and earlier8.4.28 or later31 December 2028
PHP 8.38.3.36 and earlier8.3.37 or later31 December 2027
PHP 8.28.2.35 and earlier8.2.36 or laterEnds on 31 December 2026
PHP 8.1 and earlierAffected by some of the vulnerabilitiesNo fixed releases. Upgrade to a supported seriesSupport ended

※ The affected series differ for each vulnerability. For example, CVE-2026-129474 and 129182 in the table below affect only PHP 8.5. On the other hand, some issues such as the PHP-FPM privilege escalation (CVE-2026-129291) are said to also affect some versions of PHP 8.1, but there is no fixed release for them.

※ PHP 8.6.0, the new series (published on 19 November), is not listed among the affected versions in any of these advisories. Its security support runs until 31 December 2030.

Even if you updated in October, you need to update again

The fixed releases of 21 October (8.5.12, 8.4.27, 8.3.36 and 8.2.35) fixed the two PHP2Shell issues. These releases are also affected by the 17 new issues. Also, PHP distributed by Linux distributions (Red Hat, Ubuntu and so on) or by rental servers (shared hosting) may include the fixes even if the version number is different. Check the information from your provider.

The seven Critical issues and the conditions for exploiting them

We have summarised what is written in the PHP development team's advisories (on GitHub). All of them become dangerous only "when certain conditions are met", and whether your system meets those conditions depends on the server settings and how the app is built.

VulnerabilityWhat it isMain conditionsAffected series
CVE-2026-129289Request smuggling in PHP-FPM. Someone may be able to run PHP programs without logging inWhen the web server is set to reuse its connection to PHP-FPM (such as fastcgi_keep_conn on in nginx or enablereuse=on in Apache), and the app does not read the submitted data (php://input) all the way to the end8.2 to 8.5
CVE-2026-115560A mismatch in session storage formats may allow arbitrary code execution (already disclosed on 23 October)When the session upload progress feature is enabled, and the same session is read and written in different storage formats8.2 to 8.5
CVE-2026-126714If writing a session file stops partway, arbitrary code execution may be possibleWith the default file storage (files), when an attacker can influence the contents of the session. Usable pieces (a gadget chain) on the app side are also needed8.2 to 8.5
CVE-2026-129496A mistake in handling time zone information (use of memory after it has been freed) may allow arbitrary code executionWhen a settings warning (such as an invalid date.timezone) appears at startup, and errors are logged to a file8.2 to 8.5
CVE-2026-129474Error logging in magic methods (such as __call()) may allow arbitrary code executionWhen zend.exception_ignore_args=0. With the value 1 from the production settings file (php.ini-production), this attack does not work8.5 only
CVE-2026-129182Something missed by the October fix (PHP2Shell). Memory corruption may be possibleWhen special PHP settings (memory limit or compression settings) are layered on per directory8.5 only
CVE-2026-129481If session shutdown processing stops partway, memory corruption may be possibleWhen a fatal error occurs in the app's processing that is called when the session ends8.3 to 8.5

※ The severity is the rating given by the PHP development team in its GitHub advisories. CVSS scores had not been published at the time we checked.

If you use Laravel

The advisory for CVE-2026-129474 mentions Laravel "facades" and some Magento features as examples of processing that goes through magic methods. However, it also says that an attack on a whole Laravel or Magento app has not been demonstrated. This vulnerability affects only PHP 8.5, and it can be prevented with zend.exception_ignore_args=1. In any case, updating PHP is the most reliable step.

The other 10 issues (High and Medium)

Four issues rated High and six rated Medium have also been fixed. The main ones are as follows.

  • PHP-FPM privilege escalation (CVE-2026-129291, High): an attacker who can run PHP programs on the server may be able to take the privileges of the FPM parent process (in many cases, root). It applies when catch_workers_output is enabled. Take particular care in environments where several users share one server, such as rental servers.
  • A way to get past PHAR signature checks (CVE-2026-128090, High): even if the contents of a signed PHAR file are altered, this may go unnoticed.
  • URLs written in capitals as "HTTPS://" are not encrypted (CVE-2026-128064, High): when communicating with outside services using file_get_contents() or similar, passwords and tokens may be sent without encryption.
  • Specially crafted responses from an outside server can make processing heavy (CVE-2026-127960, High)
  • A mistake in PHP-CGI's PATH_INFO handling (CVE-2026-129538, Medium): a single request without logging in may be able to stop processing. The workaround is cgi.fix_pathinfo=0.

Settings for when you can't update right away

The PHP development team gives a temporary workaround for each vulnerability. None of them are a substitute for updating. After changing settings, restart PHP-FPM or similar, and check that the site works correctly.

  • session.upload_progress.enabled=0 (turns off session upload progress). This becomes the default in the fixed releases, but if it is enabled in your settings file, that setting takes priority
  • Stop reusing the connection between the web server and PHP-FPM (in nginx, do not enable fastcgi_keep_conn)
  • In production, set zend.exception_ignore_args=1 (PHP 8.5)
  • Get rid of any settings warnings that appear when PHP starts, or send error logs somewhere such as syslog
  • If you use PHP-CGI, set cgi.fix_pathinfo=0
  • Put as little user-submitted data into sessions as possible

What to do today, and what to ask your development company

  1. List everything that runs on PHP

    Write down your website (including WordPress), contact forms, booking or membership management systems, and so on.

  2. Check the versions

    For WordPress, you can check in the admin screen under "Tools" → "Site Health" → "Info" → "Server". For systems that were built for you, ask your development or maintenance company.

  3. Ask for an update to the fixed release

    Tell them, "Please update to the security releases such as PHP 8.5.13 released on 19 November." Check that everything works in a test environment before putting it into production.

  4. If you can't update right away, review the settings

    Have them consider the "Settings for when you can't update right away" above, to suit your configuration.

  5. Plan a move off PHP 8.2 and 8.1 or earlier

    Support for 8.2 ends at the end of December. For costs and how to proceed, see "PHP upgrade cost and process".

How this relates to PHP2Shell (October)

PHP2Shell in October (CVE-2026-109618 and 109619) was added by CISA on 26 October to its list of "vulnerabilities confirmed to have actually been exploited", and products with PHP built in, such as firewalls, were also targeted. The 17 issues this time are different vulnerabilities, but they include some, such as CVE-2026-129182 and 129481, that fix things missed by the October fix. The October response is explained in "What to Do About the PHP Vulnerability", and an example of a product being targeted in "What to Do About the Check Point Vulnerability".

Leave it, or act now?

If you leave it

  • In configurations that meet the conditions, someone may be able to run programs from outside
  • If the attack methods are published, the range of targets may widen
  • PHP 8.2 will stop receiving fixes from the new year

If you update and review the settings

  • All 17 issues are fixed at once
  • Unused features and risky settings are cleaned up
  • It becomes easier to plan the next version upgrade

How Digi Dinos can help

Digi Dinos is a company that supports DX, security, and the operation and maintenance of systems. We are ISO 27001 certified, and we also handle maintenance of PHP systems (Laravel and others), server operations, and monitoring 24 hours a day, 365 days a year (NOC). Our team works in Japanese.

  • Checking versions and settings: we check your PHP version and whether your PHP-FPM and web server settings meet the conditions for these issues.
  • Carrying out the update: we check that everything works in a test environment, then update production.
  • Upgrading old PHP: even for systems whose original developer can no longer be reached, we can read the source code and take them over.

Is your PHP safe? Even a simple question is welcome (free consultation).

From checking your versions to planning the update, with guidance in Japanese.

Frequently asked questions

We updated to the PHP2Shell fixed release in October. Do we need to update again?

Yes. The October fixed releases (8.5.12, 8.4.27, 8.3.36 and 8.2.35) are also affected by these vulnerabilities. Update to 8.5.13, 8.4.28, 8.3.37, 8.2.36 or later.

Are we safe if we use the default settings?

The PHP development team says that many of the Critical issues require non-default settings or uncommon configurations. However, some involve sessions saved to files (the default), and IPA also urges people not to assume they are safe just because they use the default settings. Update.

We use a rental server. Do we need to do anything ourselves?

PHP updates are often handled by the hosting company, but the user may be the one who chooses which PHP series to use (8.2, 8.3 and so on). Check the control panel and the company's notices, and if you are using 8.2 or earlier, whose support is ending, switch to a newer series. Switching can sometimes stop a site from working, so consult your development company.

Are these being used in actual attacks?

As of 21 November 2026, we have not found official information that these 17 issues have been used in actual attacks. They are not in CISA's KEV either. However, exploitation of PHP2Shell in October was confirmed within a few days of its disclosure. We recommend updating early.

Related articles