Answer Brief
The PHP security team announced a security release for all supported versions, scheduled for 14:00–14:30 UTC on November 19, 2026. The highest severity is Critical, but the team says exploitation requires a non-default setting or uncommon configuration. Details and fixed versions arrive with the release; teams should prepare to update.
Signal Timeline
A quick visual path for analysts before reading the full brief.
- 1
A PHP security release fixed CVE-2026-109618 and CVE-2026-109619, two vulnerabilities that could allow remote code execution without authentication. It was moved up one day from October 22 after information leaked before disclosure.
- 2
The PHP development team said it would publish a detailed advisory for CVE-2026-115560 with the next release, and recommended session.upload_progress.enabled=0 until then.
- 3
The PHP security team announced the upcoming security release (UTC date given by the source).
- 4
The security release was scheduled for 14:00–14:30 UTC (23:00–23:30 Japan time). PHP 8.6.0 stable was also planned for the same day.
Executive Summary: The PHP security team announced a security release for all supported versions, scheduled for 14:00–14:30 UTC on November 19, 2026. The highest severity is Critical, but the team says exploitation requires a non-default setting or uncommon configuration. Details and fixed versions arrive with the release; teams should prepare to update.
Why It Matters
ITmedia reports that the PHP security team pre-announced a security release for all supported branches. The release was set for 14:00 to 14:30 UTC on November 19, 2026, which is 23:00 to 23:30 in Japan. The highest severity among the fixes is Critical. The announcement is notable because it follows an October emergency that, per the source, pushed many organizations into urgent maintenance.
The key distinction is the exploitation condition. The PHP team says the Critical-rated issue can be exploited only with a non-default setting or an uncommon configuration. That differs from the October pair, CVE-2026-109618 and CVE-2026-109619, which the source describes as remote code execution risks without authentication. They affected every PHP runtime that handles web requests, and both carried a CVSS v4.0 score of 9.2. The new announcement does not describe the same breadth, though the source gives no technical details yet.
Technical Signal
Readers should be careful with the word Critical. It describes the maximum severity the team assigned, not a confirmed exposure level for any given environment. ITmedia stresses that organizations cannot tell whether they are affected until details are published. That makes the gap between announcement and disclosure an uncertainty window. Teams can prepare, but they cannot responsibly claim they are safe or exposed.
The operational ask from the PHP team is simple: be ready to update quickly once the release lands. The release is part of a four-week regular cycle, so this is a scheduled event rather than an out-of-band fix. Even so, the source frames it against October's experience. For operators, that argues for having change windows, testing paths and ownership settled before the fixed versions appear, not afterward.
Operational Impact
One concrete item ties back to October. On October 23 the development team said a detailed advisory for CVE-2026-115560, a session upload progress issue, would be published with the next release. The team described it as arising only from a special combination of configuration and application code. Until then it recommended session.upload_progress.enabled=0. The source adds that this setting was also a mitigation for CVE-2026-109619, so teams that applied it in October need no further action for that purpose. The source does not say that CVE-2026-115560 is the Critical issue in the new release, so readers should not assume a link.
For Japan-facing operators, the source itself supplies the local context. IPA issued an advisory in October urging prompt application, and asked organizations to take inventory of programs they develop or run that use PHP. That inventory step is the sort of preparation that pays off now. A team that already knows which applications run on which PHP branch can map the new advisory to its estate within hours of publication. The source also recalls that many companies carried out emergency maintenance in the evening of October 21. Its related coverage notes that the prime minister posted on social media urging patching. These are source-reported details, not conclusions drawn here.
What To Watch
Affected teams include web application developers, platform and hosting operators, vulnerability management staff and change managers. The supported branches are PHP 8.5, 8.4, 8.3 and 8.2. PHP 8.2 reaches end of support on December 31, 2026. As a monitoring implication, anyone still on 8.2 may want to consider how this release interacts with their migration plans, since the support window is short. The source does not say whether an 8.2 fix will be available beyond this release.
The boundaries of what is known are narrow. The source does not give the fixed version numbers, the vulnerability class of the Critical issue, a CVE ID for it, the exact non-default settings, or any evidence of exploitation. It also does not say whether the release has since been published as scheduled, since it was written ahead of the event. Readers should not infer exploit availability, remote code execution or scope from the Critical label alone.
What to watch next: the PHP Group's release announcement and advisories, which the source lists as related links, including the upcoming-release notice and the session upload progress advisory. Check the fixed versions for each supported branch, read the conditions needed for exploitation, and compare them with your configuration baselines. The source also notes that PHP 8.6.0 stable was planned for the same day. That is a separate release, but it may add to the workload for teams that track new versions. Until the details are public, the sensible posture is to prepare, confirm inventory, and keep the October mitigation in place where it applies.
Event Type: security
Importance: high
Affected Companies
- The PHP Group
- ITmedia
- IPA
Affected Sectors
- Web application development
- Enterprise IT
- Software
Key Numbers
- Supported PHP branches: PHP 8.5, 8.4, 8.3, 8.2
- CVSS v4.0 score for October's CVE-2026-109618 and CVE-2026-109619: 9.2
- PHP 8.2 support end: December 31, 2026
Timeline
- A PHP security release fixed CVE-2026-109618 and CVE-2026-109619, two vulnerabilities that could allow remote code execution without authentication. It was moved up one day from October 22 after information leaked before disclosure.
- The PHP development team said it would publish a detailed advisory for CVE-2026-115560 with the next release, and recommended session.upload_progress.enabled=0 until then.
- The PHP security team announced the upcoming security release (UTC date given by the source).
- The security release was scheduled for 14:00–14:30 UTC (23:00–23:30 Japan time). PHP 8.6.0 stable was also planned for the same day.
Frequently Asked Questions
What did the PHP security team announce?
The team announced a security release for November 19, 2026, between 14:00 and 14:30 UTC. It is part of the four-week regular release cycle and fixes a vulnerability affecting all supported versions. Fixed version numbers and technical details are to be published with the release.
Is this the same as the October PHP emergency?
According to ITmedia, no. October's CVE-2026-109618 and CVE-2026-109619 could allow remote code execution without authentication and scored 9.2 under CVSS v4.0. This time, the team says the Critical issue needs a non-default setting or uncommon configuration to be exploited.
Which PHP versions are covered?
The source says the fix affects all supported versions. Those are PHP 8.5, 8.4, 8.3 and 8.2. PHP 8.2 is scheduled to reach end of support on December 31, 2026, so teams on that branch should plan accordingly.
What should teams do before details are published?
The PHP team asks users to prepare to update promptly after release. Because exposure cannot be judged until details appear, teams can check which PHP versions they run. If they have not already, they can apply session.upload_progress.enabled=0 as the team advised for CVE-2026-115560 in October.
How does CVE-2026-115560 relate to this release?
On October 23 the PHP team said a detailed advisory for CVE-2026-115560, a session upload progress issue, would accompany the next release. It said the issue needs a special mix of configuration and application code. The source does not confirm that this CVE is the Critical issue in the new release.