PHP posted a further note on October 23. It says the full advisory waits for the next regular release.
PHP's October 23 note assigns CVE-2026-115560 and calls the path unlikely. A full advisory waits for the next regular release. This page does not print settings.
The short version
PHP's October 23 note assigns CVE-2026-115560 and says the path is unlikely, needs an unusual mix of configuration and application code, and waits for a full advisory with the next regular release. People who already followed the October 21 guidance have no new action. Those October 21 releases fixed a different pair of flaws. This page does not print settings.
A note, not a fourth version number
On October 23, 2026 the PHP project added an informational advisory to its news archive. The heading is about session upload progress. The body assigns CVE-2026-115560, says the situation is unlikely in practice, and says the project will publish a full advisory with the next regular bugfix release rather than ship another emergency. The PHP Foundation pointed at the same archive note the same morning. The Hacker News wrote it up as a further issue two days after the emergency releases. This paper's October 21 brief is those releases, CVE-2026-109618 and CVE-2026-109619, and the versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. The October 23 note says it is not that pair.the October 21 archive.
What PHP is willing to say about scope
PHP says the issue can occur only under an unusual combination of configuration and application code, and that applications which never change the handler at runtime are not exposed through this path and can leave the related feature enabled. That is a scope statement. It is also as far as this page will go. The project names the feature, session upload progress, and it points people who already applied the October 21 mitigation back at that mitigation. Printing the settings again would turn a follow-up note into a worksheet. The Hacker News prints them. The PHP page prints them. This page cites both and does not.an identifier is not a recipe.
What is still missing, on the news account
The Hacker News says PHP has not stated which versions are affected, which future releases will contain the fix, or a severity score, and has not said whether the cause matches CVE-2026-109619. An informational note that withholds the score is a choice. Readers who want a CVSS figure will not find one in the October 23 archive entry this page is using. The outlet also says it knows of no exploitation of the new identifier, and that the attacks being discussed target the earlier flaws. This page adopts that split: two patched identifiers, one noted identifier, no emergency tarball for the third.what a score does not say.
The nickname stays on the earlier story
Coverage of the October 21 pair has traveled under a nickname. The October 23 note does not need that nickname to be identified. It has an identifier, a date, and a promise of a later advisory. Using the nickname here would glue a new, narrower note to a patched pair and invite the reader to think the emergency is repeating. PHP's own heading does not do that. The Hacker News headline does. This page follows the archive on the question of whether this is an emergency. PHP says it is not, because the setup is unlikely and the fix can ride the regular cycle.the scheduled release already happened.
Who the project says can wait
Someone who already took the October 21 advice, PHP says, keeps that advice in place and does nothing new for this identifier. Someone whose application never changes the handler while running, PHP says, is outside the path. Someone who cannot tell whether the application changes that handler has a question for the people who wrote the application, not a new version number to type today. Distributions that shipped the October 21 packages have not, on this note, been handed a new package. The next regular release is the document that would name versions.a patch window and the version.
What The PHP Foundation added
The foundation's public post points at the archive and tells operators the new identifier is the unlikely path, and that the earlier mitigation still covers it. A foundation post and the project archive are not fully independent, and this page says so. The Hacker News is the outside account. Two of the three sources sit with the project and its foundation. That is enough to file, and it is not three unrelated investigations. Where the foundation is shorter than the archive, the archive is the note.what an advisory must name.
Who is in scope
Operators of PHP who serve web requests and who are trying to tell the October 21 releases from the October 23 note. Application authors who change session handling at runtime, as the class PHP says would have to look. People who already applied the October 21 guidance, as the class PHP says can stop. Hosts that do not run PHP are out of scope. This page does not extend the note to a language runtime that is not PHP.Node's October release is a different project.
What stays on the record
October 23, 2026 informational note on php.net. CVE-2026-115560. PHP's words: unlikely, unusual combination of configuration and application code, full advisory with the next regular release, no new action if the October 21 guidance is already in place. October 21 pair remains CVE-2026-109618 and CVE-2026-109619, fixed in 8.5.12, 8.4.27, 8.3.36, and 8.2.35. The Hacker News: no score, no affected-version list, no known exploitation of the new identifier in its story. PHP Foundation post pointing at the archive. No settings printed here.
What would move the row
The full advisory PHP promised, with versions and a score, would replace this note. A report of exploitation that names this identifier, from the project or from a second investigator, would change the unlikely. Until then the record is the archive entry, the foundation's pointer, and one news account. The short answer this page will stand on is this: PHP's October 23 note assigns CVE-2026-115560 and says the path is unlikely, needs an unusual mix of configuration and application code, and waits for a full advisory with the next regular release. People who already followed the October 21 guidance have no new action. Those October 21 releases fixed a different pair of flaws. This page does not print settings.the advisory is the story.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Do the October 21 releases fix CVE-2026-115560?
PHP says no. Those releases are the earlier pair. The new identifier waits for a later regular release and a full advisory PHP says it has not published yet.
Who does PHP say is outside the new path?
PHP says the issue needs an unusual combination of configuration and application code, and that an application which never changes the relevant handler while it is running is not on this path. This page does not list the settings that combination uses.
Did PHP score it?
The Hacker News says PHP has not given affected versions, a fixed release, or a severity score, and has not said whether the new issue shares a cause with CVE-2026-109619. Absence of a score is part of the note's shape. It is an informational advisory, in PHP's heading.
Is there a reported attack on the new identifier?
The Hacker News says it has seen no report of exploitation of CVE-2026-115560, and that attacks discussed since October 21 target the earlier pair. A claim of no known exploitation is the outlet's, tied to the date of its story.
What should someone who already updated do?
PHP says that if the October 21 guidance is already in place, no further action is required for this note. The project also says the new issue is not an emergency release. This page does not restate the guidance as a recipe.