Skip to main content
Diagram: the PHP patch release by the numbers. Illustration: SecurityXP

PHP 8.6.0 Carries the Fix for CVE-2026-126714, the 9.2-Rated Flaw October's Releases Left Open

· 4 min read · SecurityXP

Key Facts

  • CVE-2026-126714 is rated 9.2 out of 10 on the CVSS 4.0 scale by PHP's maintainers.
  • PHP 8.6.0, released today, includes the fix; the October 21 releases do not contain it.
  • The October 21 releases fixed two critical flaws known as PHP2Shell.
  • The official end-of-life mitigation branches for 7.4, 8.0 and 8.1 are not affected, but older unpatched builds of those versions are, according to the company.
  • BleepingComputer reported that the PHP security updates fix 18 flaws, including critical remote code execution bugs.

PHP 8.6.0, released today, includes the fix for CVE-2026-126714, a flaw that PHP’s maintainers rate 9.2 out of 10 on the CVSS 4.0 scale. The PHP releases published on October 21 do not contain that fix.

The distinction is small on paper and large in practice. An administrator who updated on the strength of October’s advisories is running code with this flaw still present, and will keep running it until today’s release is installed.

What follows is a reading of the public record: the maintainers’ changelog and advisory, the GitHub security advisory filed against the PHP source tree, and the depthfirst research write-ups.

The Score and the Version Number

The flaw is tracked as CVE-2026-126714. The rating of 9.2 out of 10 is on the CVSS 4.0 scale, and it comes from PHP’s own maintainers rather than from a downstream scanner or an aggregator. On a scale that stops at 10.0, a score in that band sits at the top of the range.

Two version numbers matter here, and they are easy to swap by accident. PHP 8.6.0, also released today, includes the fix. The October 21 releases do not. The numbering is close enough that a changelog skim can produce the wrong conclusion, so the version and the date have to be read together.

What October’s Releases Did and Did Not Cover

The October 21 releases were not trivial. They fixed two critical flaws known together as PHP2Shell. BleepingComputer’s coverage of the PHP security updates put the number of flaws fixed at 18, including critical remote code execution bugs.

That is a substantial batch, and it explains why so many operators treated October as settled. The record now separates two things that are easily confused. A release can be current, widely deployed, and still incomplete. The October 21 PHP releases, which fixed two critical flaws known as PHP2Shell, do not contain this fix.

Patching, in other words, is a property of a flaw and a build, not of a release date. A branch can be described as up to date while a specific critical issue on that branch remains open.

What “Not Affected” Means for the End-of-Life Branches

According to the company, the official end-of-life mitigation branches for 7.4, 8.0 and 8.1 are not affected, but older unpatched builds of those versions are.

That sentence covers two different populations. The branch in its current official state is not affected. A build cut from that branch before the relevant change is affected. Operators who have pinned an old build, or who are running a distribution package built from one, are in the second group even though the version string looks safe.

The same reading applies to October. Servers updated then remain affected until they install today’s releases. The update was real, and it closed two critical flaws. It did not close this one.

The Session File at the Center of It

The public record describes the flaw from two directions. The GitHub security advisory filed against php/php-src states the outcome plainly: partially overwritten session files can lead to remote code execution. The depthfirst research write-up takes the other route, with the title “From Interrupted Session Writes to Remote Code Execution.”

Between those two descriptions sits the sequence an operator needs in order to judge exposure: which write, interrupted under what conditions, and read back as code by which path. That sequence is documented in the research write-up rather than in the advisory’s summary line.

What the advisory establishes without qualification is the trust boundary. A session file is written by the runtime on behalf of a visitor, and a flaw in that write ends in code execution. That is why the severity lands where it does, and why the flaw survived a round of patching that was aimed at critical remote code execution bugs.

What to Do

The remediation guidance is short. Install the fixed release for your branch. For the 8.6 line, that release is 8.6.0, which includes the fix.

Deployments that took the October 21 releases remain affected until they install today’s releases. This is the step most likely to be skipped, because the October work is already done and recorded.

Operators on the end-of-life branches should confirm the build they are actually running, not the branch name on the support page. The official end-of-life mitigation branches for 7.4, 8.0 and 8.1 are not affected, but older unpatched builds of those versions are, according to the company.

The plain version of the lesson: read the advisory for the flaw, not the release note for the date. October fixed two critical flaws and 18 in total, and it was still not the whole of the problem.

Tags: CVE-2026-126714 php remote-code-execution patch-management vulnerability-disclosure CVSS

Sources & References

S SecurityXP
SecurityXP Cybersecurity News & Analysis

SecurityXP delivers cybersecurity news, vulnerability analysis, data breach reports, and threat intelligence.

Security Digest

The most important cybersecurity stories, CVE alerts, and threat intelligence — one concise email. Unsubscribe anytime.

Related Articles