PHP 8.6.0 and 8.5.13 fix seven Critical flaws; two pages say RCE not demonstrated; four cite AI assistance
PHP 8.6.0, 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix seven flaws that PHP's GitHub advisories rate Critical, all 9.2 on CVSS 4.0. Two pages say code execution has not been demonstrated, four report headers cite AI assistance, and one is an incomplete fix of October's flaw.
By Parminder Kumar Sharma · LinkedIn · · 20 min read
Seven Critical advisories: two without demonstrated code execution, four citing AI assistance
Seven GitHub advisories in php/php-src, each dated Nov 19, 2026 and each marked Critical, sit behind PHP 8.6.0, 8.5.13, 8.4.28, 8.3.37 and 8.2.36. All seven score 9.2 on CVSS 4.0 with attack requirements printed as Present; attack complexity is High on four and Low on three (derived counts). Reading each Impact section, this site counts two pages that say code execution has not been demonstrated, four that describe a demonstration with conditions, and one that prints neither (derived). Four pages carry the line "This report was submitted with AI assistance"; three do not. The saved advisory pages were read at about 17:23 to 17:24 UTC on 19 November 2026; each prints a date and no time of day.
One of the seven, CVE-2026-129481, says it "is an incomplete fix for CVE-2026-109619", the October flaw that PHP fixed in the 21 October releases, 29 days before this one (derived: 21 October to 19 November). The more useful question is what each page says it takes to reach each flaw, because "Critical" is one word covering seven different sets of conditions.
What this does not establish: it does not say any of the seven is exploited, and no saved page says so. A Critical rating is a severity label; the pages print conditions beside it. It also does not say how the AI assistance was used. The pages print the line and nothing else about it, and this site comments on no product. php.net's one line notices say only "This is a security release"; the technical content is in the GitHub pages. PHP 8.6.0 is, in the words of the 12 November notice, "the first GA release" of the 8.6 branch; the saved change log lists the seven fixes under it, and under each older branch the advisories list.
What was released, and how many entries the change log counts
The PHP 8 change log dates five versions 19 Nov 2026: 8.6.0, 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The 18 November notice gave a window of "between 14:00 and 14:30 UTC" (a 30 minute window, derived) and called the releases part of PHP's regular four week cycle; it said "The highest severity is CRITICAL" and that technical details and fixed version numbers would be published with the releases.
Security entries in the saved PHP change log, read at about 17:23 UTC on 19 November 2026. Counts are this site's, made by counting lines that name a GHSA id in each version's block.
| Version | GHSA entries | Of them, the seven Critical |
|---|---|---|
| 8.6.0 | 17 (plus one uriparser line naming a CVE) | 7 |
| 8.5.13 | 17 (plus the same uriparser line) | 7 |
| 8.4.28 | 14 | 5 |
| 8.3.37 | 13 | 5 |
| 8.2.36 | 12 | 4 |
The count differs between outlets, and this site resolves none of it. SecurityWeek says the releases carry fixes "for all critical bugs and for 10 high and medium-severity flaws" besides the seven, which makes 17. Other outlets, which this site did not read, say 18 flaws. This site's own count of the change log is 17 entries naming a GHSA id in each of 8.6.0 and 8.5.13, seven Critical and ten others (derived: 17 minus 7), and a further line, "Upgrade to uriparser 1.0.3. (CVE-2026-48841)", that names a CVE but no GHSA, which makes 18 lines naming a CVE. That 18 matches the other outlets' figure only as arithmetic; this site does not know how they counted. The change log prints no severity, and this site did not read the ten other advisories, so "high and medium" is SecurityWeek's relay.
Which branches, and what each page says it takes
The matrix draws what the seven pages print. Dashed cells are where a page prints nothing. For 8.6 no page prints a range, because the pages list affected and patched versions only for the 8.2 to 8.5 branches; the change log is where 8.6.0 carries the fixes.
Branch counts, derived from the printed affected ranges: PHP 8.2 is affected by 4 of the seven, 8.3 by 5, 8.4 by 5 and 8.5 by all 7. Two advisories, the global after shutdown and the magic method backtrace, list PHP 8.5 only. The use-after-free after an interrupted session shutdown lists 8.3 and later, and its page says PHP 8.2 "does not contain the affected session filename field". The 8.2.36 change log block lists four of the seven. The session serializer page adds that session upload progress arrived in PHP 5.4.0, "so older unsupported releases may also be affected"; no page says which older release is.
What each page says must be true, and what it says about demonstrated impact. Quotations are short and exact; the rest is this site's plain wording of the Summary and Impact sections.
| Advisory | What the page says it takes | What the page says about demonstrated impact |
|---|---|---|
| Session serializer mismatch (CVE-2026-115560) | A "configuration-dependent deserialization issue". Session upload progress, a writer and a reader using different serializers, and an application with a suitable object chain. A setup that never switches serializer "can still be affected" if another application writes incompatible data into the same store. | Command execution reproduced using object classes from two third party libraries on 8.2.35, 8.3.36, 8.4.27 and 8.5.12 (the releases before this one). Exploitability depends on the classes the reader has. |
| Interrupted session shutdown (CVE-2026-129481) | PHP 8.3 and later. An attacker who can make session cleanup fail; a later request handled by the same worker. Authentication requirements "depend on the application path". The demonstrated setup has OPcache disabled. | Memory corruption or a worker crash. Code execution "through this specific field has not been demonstrated". |
| Global after shutdown (CVE-2026-129182) | PHP 8.5 only. A fatal diagnostic during later shutdown work repopulates a global; an early diagnostic in a later request in the same worker reads it. | The cases "demonstrate heap use-after-free and worker crashes". Code execution through these entry points "has not been demonstrated". |
| Magic method backtrace (CVE-2026-129474) | PHP 8.5. fatal_error_backtraces=1 (on by default in 8.5) and zend.exception_ignore_args=0. Enough request data to influence memory, a reachable magic method and a fatal error at the right point. | "Remote code execution has been confirmed" on 8.5 and later, with usable memory addresses needed despite randomisation. A complete Laravel or Magento install: not demonstrated. |
| Partially overwritten session files (CVE-2026-126714) | The files session handler, "PHP's default". Attacker influence over session data, an interrupted write at a useful point, and an application with a suitable object chain. | The Impact section says successful exploitation "can execute code" and prints neither a demonstration nor its absence. |
| PHP-FPM request smuggling (CVE-2026-129289) | A front end with persistent backend connections and an application path that opens php://input without reading it fully. Standard nginx and Apache setups that close the connection are not affected by the demonstrated attack. | The PHP-FPM attack is called demonstrated. For LSAPI the page "does not establish arbitrary code execution". |
| Timezone cache (CVE-2026-129496) | A startup diagnostic, PHP error logging to a file, and an early diagnostic in a fresh worker. "On affected configurations". | Code execution "demonstrated locally" in FPM and Apache mod_php with known addresses and extra configuration assumptions. |
Critical, and "not demonstrated": a rating beside a gap
Two pages, CVE-2026-129481 and CVE-2026-129182, rate the flaw Critical and 9.2 and say in the Impact section that code execution through these routes has not been demonstrated. Both say the use-after-free can corrupt memory or crash a reused worker, and the first says it "could potentially lead to remote code execution". The score covers the worst case the base metrics allow, high impact on confidentiality, integrity and availability; the sentence beside it describes what was shown. A reader who ranks by the word alone treats these two like the PHP-FPM page, which describes a demonstrated attack. A reader who ranks by the sentence alone risks treating "not demonstrated" as "safe", which the pages do not say either.
The attack complexity metric points the same way for some pages and not others (derived from the printed vectors). The two "not demonstrated" pages differ: 129481 is High, 129182 is Low. Of the four pages that describe a demonstration, three print extra conditions beside it: the magic method page needs usable memory addresses, the timezone page needs known addresses and "additional configuration assumptions", and the session serializer page needs the reader to have a suitable class. The PHP-FPM page is the one that says the attack "does not require memory corruption, knowledge of memory addresses or a race condition"; it is also Low.
The pages themselves warn against the shortcuts. The magic method page says "The presence of a framework, a magic method, or a large request body alone does not establish exploitability", and names Laravel facades and Magento guest shipping estimation only as paths that show existing applications reach magic method calls.
Against the 18 November sentence: where each page agrees
On 18 November php.net said: "The issues rated CRITICAL require either non-default configuration or uncommon setups." The advisories print the conditions; the table sets each beside that sentence. The comparison is this site's reading, not PHP's. The words "non-default" and "uncommon" are PHP's, and no page measures how common any setup is.
Each advisory's printed conditions beside the 18 November php.net sentence, read on 19 November 2026. The last column is this site's reading.
| Advisory | A condition beyond the bare version | Reading against the sentence |
|---|---|---|
| CVE-2026-115560 | Session upload progress in use, mismatched serializers, a suitable object chain in the reader. | Agrees: the page says "configuration-dependent". It adds that a setup with no runtime switch can still be affected. |
| CVE-2026-129481 | A way to make session cleanup fail; same worker; OPcache disabled in the demonstration. | The page prints no setting and no word on how common the failing path is. |
| CVE-2026-129182 | PHP 8.5 and a fatal diagnostic during shutdown work. | The page prints no default. The 129474 page says fatal error backtraces are on by default in 8.5. |
| CVE-2026-129474 | Two settings, one of them the 8.5 default; php.ini-production sets the other so that the path is closed. | Depends on the ini file in use: with PHP's built in defaults both conditions can hold, as the page prints them. |
| CVE-2026-126714 | Attacker influence over session data, an interrupted write, an application with a suitable object chain. | No non-default PHP setting is printed: the files handler is PHP's default. The uncommon part is application code. |
| CVE-2026-129289 | A front end that keeps backend connections open and an application path that leaves the body unread. | The page says no "non-default PHP configuration" is needed; the non-default part sits in the web server setting. |
| CVE-2026-129496 | A startup diagnostic, error logging to a file, an early diagnostic in a fresh worker. | Agrees in form: "On affected configurations". The page prints no count of how many there are. |
Counting the last column (derived): three pages, 129474, 126714 and 129289, print that the PHP side of the condition is a default or needs no non-default PHP configuration, and print the unusual part elsewhere: the ini file, application code, the front end. Four pages, 115560, 129481, 129182 and 129496, print conditions without saying whether they are default. None of the seven pages says how many sites meet its conditions.
The October flaw: an incomplete fix, an informational notice, and 29 days
The 21 October releases (8.5.12, 8.4.27, 8.3.36 and 8.2.35) fixed two critical flaws, one of them CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp, also scored 9.2 with attack complexity High, read from an earlier copy this site saved on 26 October). Twenty nine days later (derived: 29), two of the new advisories describe themselves as reaching further. CVE-2026-129481 calls itself an incomplete fix for it. CVE-2026-129182 says that PHP 8.5.12 fixed a generic use-after-free of a global by clearing it during shutdown, and that "Further scenarios have been discovered" in which a fatal diagnostic during later shutdown work repopulates it. The saved CVE-2026-115560 page says its flaw is "separate from" CVE-2026-109619.
The October release had been announced a day earlier, on 20 October, for 14:00 UTC on 21 October. On Friday 23 October php.net posted an "Informational advisory: Session upload progress" naming CVE-2026-115560. It called the flaw an "unlikely RCE vector", asked readers to switch session upload progress off until the next regular release, and said the issue "can only occur under an unusual combination of configuration and application code". It also said PHP would handle it in the regular cycle and publish a full advisory with the next release. That release came 27 days later (derived), and the full advisory is the Critical, 9.2 page of 19 November.
CVE-2026-115560 as php.net described it on 23 October (earlier copy saved on 26 October) and as the GitHub advisory prints it on 19 November (saved at about 17:23 UTC). Quotations are exact. This site does not decide which framing is right.
| Point | 23 October notice | 19 November advisory |
|---|---|---|
| Rating | An "unlikely RCE vector"; no score printed. | Critical, CVSS 4.0 9.2, attack complexity High, attack requirements Present. |
| Who is exposed | "Applications that never change the serialize handler at runtime can keep the feature enabled." | "An application that never changes its serializer at runtime can still be affected" if another application or process writes incompatible data into the same session store. |
| Demonstrated | Not described. | Command execution reproduced with object classes from two third party libraries on the previous releases. |
| Remedy | Switch session upload progress off until the next regular release. | Upgrade; the fix turns session upload progress off by default, and "an explicit setting overrides the new default". |
SecurityWeek, a secondary this site read at about 16:31 UTC on 19 November, describes CVE-2026-109619 as one of the two October flaws "now widely exploited". No saved page from PHP or GitHub says that, and this site neither repeats it as fact nor tests it. The same article says the session flaw was "publicly disclosed last month, two days after PHP2Shell patches landed", which fits the 21 and 23 October dates above.
The AI assistance line: four pages, no explanation
Four advisory pages print, under the title, "This report was submitted with AI assistance": CVE-2026-129481, CVE-2026-129474, CVE-2026-129289 and CVE-2026-129496. Three do not: CVE-2026-115560, CVE-2026-129182 and CVE-2026-126714 (derived counts: four and three). No page says what the assistance was, which part of the report it touched, or whether it affects the score; the php.net notices and the change log do not mention it. This site does not extend the line, and it makes no comment on any product.
The AI assistance line beside what each page says about demonstrated code execution, counted by this site from the seven pages read on 19 November 2026.
| AI line on the page | Code execution not demonstrated | Described with conditions | Page silent |
|---|---|---|---|
| Printed (4 pages) | 1 (129481) | 3 (129474, 129289, 129496) | 0 |
| Not printed (3 pages) | 1 (129182) | 1 (115560) | 1 (126714) |
Seven pages are too few to read a pattern into the table, and this site draws none. What the two rows do show is that the line does not sort the pages by demonstrated impact.
Where the sources differ
Differences between the pages, kept as differences. Nothing here is resolved by this site.
| Point | One page says | Another says, or is silent |
|---|---|---|
| How many flaws | SecurityWeek: seven critical plus 10 high and medium, which is 17. | Other outlets: 18 flaws (not read by this site). This site's change log count: 17 GHSA entries plus one uriparser line naming a CVE. |
| Where the detail is | php.net notices: "This is a security release", no technical content. | The seven GitHub advisories carry the summaries, impact and mitigations. |
| Critical against demonstrated | All seven: Critical, 9.2. | Two say code execution is not demonstrated; one is silent. |
| Exploitation of the October flaw | SecurityWeek: "now widely exploited". | No saved PHP or GitHub page says so. |
| CVE-2026-115560 | 23 October notice: unlikely, unusual combination. | 19 November advisory: Critical 9.2; a setup that never switches serializer can still be affected. |
| Versions | Some advisories list 8.2 to 8.5; one lists 8.3 and later; two list 8.5 only. | No page prints an affected range for 8.6; the change log lists all seven under 8.6.0. |
| Mitigations | Every page prints an interim measure or a front end setting. | 129481 prints pm.max_requests=1, at a performance cost, and says OPcache alone is not reliable; 129182 and 129474 name fatal_error_backtraces=0; 126714 names the upload progress setting. |
What the advisories print for defenders: versions, settings and mitigation lines
These are the defensive items the seven pages print, copied as printed and attributed in the captions. The pages print no indicators of compromise, no log line and no detection rule, and this site invents none. No trigger, request, callback, object class or code is reproduced here: the pages' Details sections were removed from the saved copies and this site does not reconstruct them.
Affected and patched versions as printed on each advisory page, read at about 17:23 to 17:24 UTC on 19 November 2026. The fixed version per branch is the same on every page that lists the branch.
| Advisory and title | Affected as printed | Patched as printed |
|---|---|---|
| CVE-2026-115560: Session serializer mismatch can lead to remote code execution | from 8.2.0 below 8.2.36; from 8.3.0 below 8.3.37; from 8.4.0 below 8.4.28; from 8.5.0 below 8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
| CVE-2026-129481: Use-after-free after interrupted session shutdown | from 8.3.0 below 8.3.37; from 8.4.0 below 8.4.28; from 8.5.0 below 8.5.13 | 8.3.37, 8.4.28, 8.5.13 |
| CVE-2026-129182: Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown | from 8.5.0 below 8.5.13 | 8.5.13 |
| CVE-2026-129474: Use-after-free in magic method backtraces can lead to remote code execution | from 8.5.0 below 8.5.13 | 8.5.13 |
| CVE-2026-126714: Partially overwritten session files can lead to remote code execution | from 8.2.0 below 8.2.36; from 8.3.0 below 8.3.37; from 8.4.0 below 8.4.28; from 8.5.0 below 8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
| CVE-2026-129289: PHP-FPM request smuggling through an unread HTTP request body | from 8.2.0 below 8.2.36; from 8.3.0 below 8.3.37; from 8.4.0 below 8.4.28; from 8.5.0 below 8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
| CVE-2026-129496: Timezone cache use-after-free can lead to remote code execution | from 8.2.0 below 8.2.36; from 8.3.0 below 8.3.37; from 8.4.0 below 8.4.28; from 8.5.0 below 8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
Fixed versions per branch, from those pages and the change log: 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0 for the new branch. PHP's 21 October notice (earlier copy) added that PHP 8.2 "reaches end of life on 31 December 2026", 42 days after these releases (derived).
First the settings the pages name, in one place. Each is an interim measure the page offers, not a fix; the pages say to set them administratively, in php.ini, the FPM pool or the web server, and to restart workers.
session.upload_progress.enabled=0 (CVE-2026-115560, CVE-2026-126714)
pm.max_requests=1 (CVE-2026-129481, PHP-FPM, at a performance cost)
fatal_error_backtraces=0 (CVE-2026-129182, CVE-2026-129474)
zend.exception_ignore_args=1 (CVE-2026-129474)
fastcgi_keep_conn left disabled (CVE-2026-129289, nginx)
enablereuse left disabled (CVE-2026-129289, Apache mod_proxy_fcgi)
Then the mitigation sentences themselves, one block per advisory in the order the saved pages give them. Read the full page before relying on any line: several carry conditions the short sentence leaves out, such as which front end setting applies.
CVE-2026-129481
For PHP-FPM, setting pm.max_requests=1 and restarting the workers prevents the demonstrated sequence from reaching a second request in the same worker, at a performance cost.
CVE-2026-129481
Enabling OPcache alone is not a reliable mitigation because scripts can still execute without being cached.
CVE-2026-115560
Otherwise, keep session.upload_progress.enabled=0 in every configuration that can write to the affected session store.
CVE-2026-115560
Set this administratively before request input is processed. Calling ini_set() from the application is too late.
CVE-2026-126714
As a temporary measure, disable session.upload_progress.enabled administratively if the feature is not needed, and limit the amount of untrusted data stored in sessions.
CVE-2026-129182
As a temporary workaround, disable fatal-error backtraces administratively with fatal_error_backtraces=0 and restart all workers.
CVE-2026-129474
As an immediate workaround for the fatal error attack, set zend.exception_ignore_args=1 in the configuration used by the affected PHP workers and restart them.
CVE-2026-129474
Setting display_errors=0 does not prevent PHP from constructing the backtrace.
CVE-2026-129289
leave nginx fastcgi_keep_conn disabled, leave Apache enablereuse disabled, or configure another FastCGI front end to close its backend connection after every request.
CVE-2026-129289
Do not expose PHP-FPM or LSAPI listeners directly to untrusted networks.
CVE-2026-129496
Sending PHP errors to a suitable logging destination that does not use this file-timestamp path, such as syslog, also avoids the demonstrated trigger.
CVE-2026-129496
Until an update can be deployed, correct configuration errors and deprecated settings that produce startup diagnostics, then restart the PHP master process and all workers.
The change log also lists ten other security entries in each of 8.6.0 and 8.5.13. The titles are printed here as the change log words them; this site did not read the ten advisories and states no severity for them.
The ten other GHSA entries in the 8.5.13 block of the saved PHP change log, with the CVE id printed beside each, read at about 17:23 UTC on 19 November 2026.
| Change log title | CVE id printed |
|---|---|
| PHP-FPM status endpoint XSS via unescaped user and script fields | CVE-2026-129292 |
| SOAP use-after-free when processing DTD entity references | CVE-2026-129506 |
| PHP-CGI out-of-bounds read and write during PATH_INFO correction | CVE-2026-129538 |
| PHAR OpenSSL signature bypass via algorithm downgrade | CVE-2026-128090 |
| Mixed-case HTTPS and FTPS URLs can expose data in plaintext | CVE-2026-128064 |
| PHP-FPM epoll use-after-free can lead to local privilege escalation | CVE-2026-129291 |
| Incorrect RFC 3986 URI serialization for oversized input | CVE-2026-129438 |
| Denial of service through folded HTTP response headers | CVE-2026-127960 |
| SOAP information disclosure through malformed array dimensions | CVE-2026-15353 |
| Double free during DOM XML serialization | CVE-2026-129501 |
What the pages state, and what they do not
Stated and not stated across the seven advisories, the php.net notices, the change log and SecurityWeek, as read on 19 November 2026.
| Topic | Stated | Not stated |
|---|---|---|
| Exploitation | SecurityWeek: the October flaw is "now widely exploited" (a secondary). | Exploitation of any of the seven in the wild; who holds working exploits. |
| Exposure | Conditions per advisory. | How many sites run an affected configuration. |
| Packages | Fixed releases of the PHP project. | Whether distribution packages and container images carry the fixes yet. |
| AI assistance | A header line on four pages. | How it was used, and whether it affected the rating. |
| Release time | A 30 minute window, 14:00 to 14:30 UTC, on the 18 November notice. | The time of day each release or advisory went up. |
| 8.6 release candidates | 8.6.0 is the first GA release; the change log lists the fixes under it. | Whether any 8.6 candidate was affected. |
| Session files advisory | Impact: successful exploitation "can execute code". | Whether code execution was demonstrated. |
What to do, in order
The first item is what the pages say. The rest are this site's suggestions, ordered by how much of your estate each one narrows.
Take this with you
Defender actions for the PHP releases of 19 November, in order
- What the pages say: upgrade each branch to its fixed release (8.6.0, 8.5.13, 8.4.28, 8.3.37, 8.2.36) and restart PHP-FPM or the web server so that old workers go.
- Inventory every PHP you run, including container base images, CMS hosts and vendor appliances, and write down each build number against those five (this site's suggestion).
- Check which of the seven apply to each branch before ranking them: 8.2 is hit by four, 8.3 and 8.4 by five, 8.5 by all seven (derived from the printed ranges) (this site's suggestion).
- Where you cannot upgrade yet, apply the interim measure each page prints (the settings block above lists them): upload progress off, fatal_error_backtraces=0 on 8.5, zend.exception_ignore_args=1, a front end that closes the FastCGI connection after every request, pm.max_requests=1 for the session shutdown flaw. Set them administratively, not from the application, and restart workers.
- After the update, look for any configuration that explicitly enables session upload progress: the page for CVE-2026-115560 says an explicit setting overrides the new default, and that readers and writers of the same session store must use the same serializer.
- Review logs for repeated worker crashes. Several pages describe worker crashes as a result of failed attempts; the pages print no log line, so look for whatever your platform records when a worker exits (this site's suggestion).
- Treat "RCE not demonstrated" as unproven, not as safe: two pages use the phrase, and neither says the flaw cannot be used.
- Plan the move off PHP 8.2: PHP's 21 October notice says it reaches end of life on 31 December 2026 (this site's suggestion).
The question the word Critical leaves open
If PHP rates seven flaws Critical while two of its own pages say code execution has not been demonstrated and its notice says they need non-default or uncommon setups, could you name today the ini setting, the front end option and the application code in your estate that would turn any one of the seven from a rating into a reachable flaw?
Key facts
Sources
- PrimaryCVE-2026-115560 advisory, Session serializer mismatch can lead to remote code execution, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryCVE-2026-129481 advisory, Use-after-free after interrupted session shutdown, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryCVE-2026-129182 advisory, Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryCVE-2026-129474 advisory, Use-after-free in magic method backtraces can lead to remote code execution, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryCVE-2026-126714 advisory, Partially overwritten session files can lead to remote code execution, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryCVE-2026-129289 advisory, PHP-FPM request smuggling through an unread HTTP request body, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryCVE-2026-129496 advisory, Timezone cache use-after-free can lead to remote code execution, read on 19 November 2026 (about 17:23 UTC): severity, CVSS 4.0 vector, affected and patched versions, Summary, Impact and Mitigation. The Details section was removed from this site's saved copyPHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- PrimaryPHP 8 ChangeLog, read on 19 November 2026 (about 17:23 UTC): the 8.6.0, 8.5.13, 8.4.28, 8.3.37 and 8.2.36 blocks dated 19 Nov 2026, counted for security entriesPHP project (php.net)accessed 2026-11-19
- Primaryphp.net news archive 2026, read on 19 November 2026 (about 17:25 UTC): the 19 Nov release notices, the 18 Nov notice, the 12 Nov RC7 notice; and the 20 to 23 Oct entries from an earlier copy saved on 26 OctoberPHP project (php.net)accessed 2026-11-19
- PrimaryPHP 8.5.13 Release Announcement, read on 19 November 2026 (about 17:23 UTC): a one paragraph notice that calls it a security releasePHP project (php.net)accessed 2026-11-19
- PrimaryGHSA-6wmf-4rv5-p3rp, the October flaw CVE-2026-109619: heading, dated Oct 21, 2026, CVSS 4.0 9.2 vector, from an earlier copy saved on 26 October (body not used)PHP project (php/php-src security advisory on GitHub)accessed 2026-11-19
- Reported byPHP Patches Seven Critical RCE Vulnerabilities, read on 19 November 2026 (about 16:31 UTC): a secondary used for the 17 count and the "now widely exploited" attribution, which no PHP page statesSecurityWeekaccessed 2026-11-19


