{"items":[{"id":653,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"[New release] php/php-src php-8.6.0 - PHP 8.6.0","summary":"(no release notes)","url":"https://github.com/php/php-src/releases/tag/php-8.6.0","published_at":"2026-11-21T02:01:51Z","updated_at":null,"fetched_at":"2026-11-21T19:15:07.553386Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":null,"vuln_ids":[],"tags":["release","repo:php/php-src"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/653","html":"https://vulnwatch.ve1ve2.com/item/653"}},{"id":654,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"[SECURITY RELEASE] php/php-src php-8.5.13 - PHP 8.5.13","summary":"Fixes advisories: GHSA-8mjj-2r7p-4hg2, GHSA-2fjv-p558-g82m, GHSA-mg3p-mxj9-g2mm, GHSA-g3vh-838c-65v7, GHSA-x8r7-mg3g-74hg, GHSA-jm4m-qfqx-967m, GHSA-mmf9-xm3v-hg2x, GHSA-f6gg-rchx-xw8j, GHSA-658j-r8rw-q6mx, GHSA-gr4f-wgx5-jpfv, GHSA-fm2m-fjf5-v3cp, GHSA-4646-p932-gw34, GHSA-qc49-hpvq-g2w6, GHSA-3mg3-cr28-46gc, GHSA-5j3f-64r7-f564, GHSA-68fq-fh7h-f8gr, GHSA-q23r-hr55-xmpg\n\n(no release notes)","url":"https://github.com/php/php-src/releases/tag/php-8.5.13","published_at":"2026-11-21T02:00:50Z","updated_at":null,"fetched_at":"2026-11-21T19:15:07.553386Z","severity":"critical","cvss_score":9.2,"epss":0.71117,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-129474","vuln_ids":["CVE-2025-1217","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129182","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129438","CVE-2026-129474","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6735","CVE-2026-91765","GHSA-2FJV-P558-G82M","GHSA-3MG3-CR28-46GC","GHSA-4646-P932-GW34","GHSA-5J3F-64R7-F564","GHSA-658J-R8RW-Q6MX","GHSA-68FQ-FH7H-F8GR","GHSA-6WMF-4RV5-P3RP","GHSA-7QG2-V9FJ-4MWV","GHSA-8MJJ-2R7P-4HG2","GHSA-F6GG-RCHX-XW8J","GHSA-FM2M-FJF5-V3CP","GHSA-G3VH-838C-65V7","GHSA-GR4F-WGX5-JPFV","GHSA-JM4M-QFQX-967M","GHSA-MG3P-MXJ9-G2MM","GHSA-MMF9-XM3V-HG2X","GHSA-Q23R-HR55-XMPG","GHSA-Q8FM-P8FX-H6R6","GHSA-QC49-HPVQ-G2W6","GHSA-RGRP-MWPX-F6RM","GHSA-V8XR-GPVJ-CX9G","GHSA-X8R7-MG3G-74HG"],"tags":["release","repo:php/php-src","security"],"cluster_id":444,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/654","html":"https://vulnwatch.ve1ve2.com/item/654"}},{"id":655,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"[SECURITY RELEASE] php/php-src php-8.4.28 - PHP 8.4.28","summary":"Fixes advisories: GHSA-g3vh-838c-65v7, GHSA-x8r7-mg3g-74hg, GHSA-jm4m-qfqx-967m, GHSA-mmf9-xm3v-hg2x, GHSA-f6gg-rchx-xw8j, GHSA-658j-r8rw-q6mx, GHSA-gr4f-wgx5-jpfv, GHSA-fm2m-fjf5-v3cp, GHSA-4646-p932-gw34, GHSA-qc49-hpvq-g2w6, GHSA-3mg3-cr28-46gc, GHSA-5j3f-64r7-f564, GHSA-68fq-fh7h-f8gr, GHSA-q23r-hr55-xmpg\n\n(no release notes)","url":"https://github.com/php/php-src/releases/tag/php-8.4.28","published_at":"2026-11-21T02:00:27Z","updated_at":null,"fetched_at":"2026-11-21T19:15:07.553387Z","severity":"critical","cvss_score":9.2,"epss":0.71117,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-129481","vuln_ids":["CVE-2025-1217","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129474","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6735","CVE-2026-91765","GHSA-2FJV-P558-G82M","GHSA-3MG3-CR28-46GC","GHSA-4646-P932-GW34","GHSA-5J3F-64R7-F564","GHSA-658J-R8RW-Q6MX","GHSA-68FQ-FH7H-F8GR","GHSA-6WMF-4RV5-P3RP","GHSA-7QG2-V9FJ-4MWV","GHSA-8MJJ-2R7P-4HG2","GHSA-F6GG-RCHX-XW8J","GHSA-FM2M-FJF5-V3CP","GHSA-G3VH-838C-65V7","GHSA-GR4F-WGX5-JPFV","GHSA-JM4M-QFQX-967M","GHSA-MMF9-XM3V-HG2X","GHSA-Q23R-HR55-XMPG","GHSA-Q8FM-P8FX-H6R6","GHSA-QC49-HPVQ-G2W6","GHSA-RGRP-MWPX-F6RM","GHSA-V8XR-GPVJ-CX9G","GHSA-X8R7-MG3G-74HG"],"tags":["release","repo:php/php-src","security"],"cluster_id":450,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/655","html":"https://vulnwatch.ve1ve2.com/item/655"}},{"id":656,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"[SECURITY RELEASE] php/php-src php-8.3.37 - PHP 8.3.37","summary":"Fixes advisories: GHSA-g3vh-838c-65v7, GHSA-jm4m-qfqx-967m, GHSA-mmf9-xm3v-hg2x, GHSA-f6gg-rchx-xw8j, GHSA-658j-r8rw-q6mx, GHSA-gr4f-wgx5-jpfv, GHSA-fm2m-fjf5-v3cp, GHSA-4646-p932-gw34, GHSA-qc49-hpvq-g2w6, GHSA-3mg3-cr28-46gc, GHSA-5j3f-64r7-f564, GHSA-68fq-fh7h-f8gr, GHSA-q23r-hr55-xmpg\n\n(no release notes)","url":"https://github.com/php/php-src/releases/tag/php-8.3.37","published_at":"2026-11-21T02:00:02Z","updated_at":null,"fetched_at":"2026-11-21T19:15:07.553388Z","severity":"critical","cvss_score":9.2,"epss":0.71117,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-129481","vuln_ids":["CVE-2025-1217","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129474","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6735","CVE-2026-91765","GHSA-2FJV-P558-G82M","GHSA-3MG3-CR28-46GC","GHSA-4646-P932-GW34","GHSA-5J3F-64R7-F564","GHSA-658J-R8RW-Q6MX","GHSA-68FQ-FH7H-F8GR","GHSA-6WMF-4RV5-P3RP","GHSA-7QG2-V9FJ-4MWV","GHSA-8MJJ-2R7P-4HG2","GHSA-F6GG-RCHX-XW8J","GHSA-FM2M-FJF5-V3CP","GHSA-G3VH-838C-65V7","GHSA-GR4F-WGX5-JPFV","GHSA-JM4M-QFQX-967M","GHSA-MMF9-XM3V-HG2X","GHSA-Q23R-HR55-XMPG","GHSA-Q8FM-P8FX-H6R6","GHSA-QC49-HPVQ-G2W6","GHSA-RGRP-MWPX-F6RM","GHSA-V8XR-GPVJ-CX9G"],"tags":["release","repo:php/php-src","security"],"cluster_id":450,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/656","html":"https://vulnwatch.ve1ve2.com/item/656"}},{"id":657,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"[SECURITY RELEASE] php/php-src php-8.2.36 - PHP 8.2.36","summary":"Fixes advisories: GHSA-jm4m-qfqx-967m, GHSA-mmf9-xm3v-hg2x, GHSA-f6gg-rchx-xw8j, GHSA-658j-r8rw-q6mx, GHSA-gr4f-wgx5-jpfv, GHSA-fm2m-fjf5-v3cp, GHSA-4646-p932-gw34, GHSA-qc49-hpvq-g2w6, GHSA-3mg3-cr28-46gc, GHSA-5j3f-64r7-f564, GHSA-68fq-fh7h-f8gr, GHSA-q23r-hr55-xmpg\n\n(no release notes)","url":"https://github.com/php/php-src/releases/tag/php-8.2.36","published_at":"2026-11-21T01:59:37Z","updated_at":null,"fetched_at":"2026-11-21T19:15:07.553389Z","severity":"critical","cvss_score":9.2,"epss":0.71117,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-129291","vuln_ids":["CVE-2025-1217","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129474","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6735","CVE-2026-91765","GHSA-2FJV-P558-G82M","GHSA-3MG3-CR28-46GC","GHSA-4646-P932-GW34","GHSA-5J3F-64R7-F564","GHSA-658J-R8RW-Q6MX","GHSA-68FQ-FH7H-F8GR","GHSA-6WMF-4RV5-P3RP","GHSA-7QG2-V9FJ-4MWV","GHSA-8MJJ-2R7P-4HG2","GHSA-F6GG-RCHX-XW8J","GHSA-FM2M-FJF5-V3CP","GHSA-GR4F-WGX5-JPFV","GHSA-JM4M-QFQX-967M","GHSA-MMF9-XM3V-HG2X","GHSA-Q23R-HR55-XMPG","GHSA-Q8FM-P8FX-H6R6","GHSA-QC49-HPVQ-G2W6","GHSA-RGRP-MWPX-F6RM","GHSA-V8XR-GPVJ-CX9G"],"tags":["release","repo:php/php-src","security"],"cluster_id":454,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/657","html":"https://vulnwatch.ve1ve2.com/item/657"}},{"id":635,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-qc49-hpvq-g2w6 / CVE-2026-129289: PHP-FPM request smuggling through an unread HTTP request body","summary":"PHP-FPM request smuggling through an unread HTTP request body\n\n### Summary\r\n\r\nPHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker.\r\n\r\n### Details\r\n\r\nFastCGI and LSAPI connections can carry more than one request. Before accepting another request on the same connection, PHP must either consume the previous request body or close the connection.\r\n\r\nOpening `php://input` creates a request-body stream, but PHP reads its contents lazily. During request shutdown, PHP incorrectly treated the existence of this stream as evidence that the body had already been handled and skipped the normal cleanup that discards unread input.\r\n\r\nAn attacker can combine this behaviour with a malformed `multipart/form-data` body that makes PHP's multipart parser stop at a predictable position. If the application then opens `php://input` without reading it to the end, attacker-controlled body bytes remain in the current backend request. This can occur in request frameworks that create an input stream before routing or authentication, even when the selected endpoint does not use the body.\r\n\r\nWhen `FCGI_KEEP_CONN` is enabled, PHP-FPM preserves the connection and starts parsing another FastCGI request. The vulnerable implementation discarded its knowledge that it was still inside an `FCGI_STDIN` record, so a FastCGI message placed at the appropriate body offset was accepted as a new request. The front end never created or authorised this request.\r\n\r\nThe forged request controls FastCGI parameters including `SCRIPT_FILENAME`, `REMOTE_ADDR` and `PHP_ADMIN_VALUE`. If the attacker knows the path of an existing PHP script, they can set `allow_url_include=1` and `auto_prepend_file=php://input`, causing the forged request's own input to be executed as PHP. The changed administrator settings can also remain active for later requests served by the same worker. The shared request-cleanup error also affects LSAPI's persistent request lifecycle, but LSAPI does not use this FastCGI parameter mechanism.\r\n\r\nThe issue was introduced with lazy `php://input` handling in PHP 5.6.0. The fix drains input according to whether the body was fully consumed, independently of whether a `php://input` stream exists. PHP-FPM additionally closes a connection instead of accepting another request when the previous FastCGI input record is incomplete.\r\n\r\n### Impact\r\n\r\nExploitation requires a front end that enables persistent backend connections and an application path that opens `php://input` without reading it fully. Relevant configurations include nginx with `fastcgi_keep_conn on`, Apache `mod_proxy_fcgi` with `enablereuse=on`, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the de\n\nAffected packages: php:sapi-fpm\nPatched: sapi-fpm 8.2.36, sapi-fpm 8.3.37, sapi-fpm 8.4.28, sapi-fpm 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6","published_at":"2026-11-19T14:08:40Z","updated_at":"2026-11-19T18:42:45Z","fetched_at":"2026-11-21T19:15:07.553372Z","severity":"critical","cvss_score":9.2,"epss":0.16138,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"sapi-fpm","vuln_id":"CVE-2026-129289","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-QC49-HPVQ-G2W6"],"tags":["repo-advisory","php","CWE-444","CWE-670","security","repo:php/php-src"],"cluster_id":463,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/635","html":"https://vulnwatch.ve1ve2.com/item/635"}},{"id":631,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-658j-r8rw-q6mx / CVE-2026-115560: Session serializer mismatch can lead to remote code execution","summary":"Session serializer mismatch can lead to remote code execution\n\n### Summary\r\n\r\nPHP's session upload progress feature can write attacker-controlled data using one session serialization format and later read it using another. A mismatched decoder can interpret part of a session key as serialized object data. An application with a suitable object gadget chain can then execute code with the privileges of the PHP worker.\r\n\r\nThis is a configuration-dependent deserialization issue, separate from the stale global state vulnerability in CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp). Session upload progress was introduced in PHP 5.4.0, so older unsupported releases may also be affected.\r\n\r\n### Details\r\n\r\nThe affected setup has the following conditions:\r\n\r\n- Session upload progress is enabled, and an attacker can submit a multipart upload to a context using `php_binary` or `php_serialize` as its session serializer.\r\n- A later or concurrent operation can access the same stored session, using the same session ID and the `php` serializer.\r\n- For code execution, the reading application has a suitable deserialization gadget chain available.\r\n\r\nThe mismatch can arise when an application changes `session.serialize_handler` to `php` before calling `session_start()`. It can also arise between separate applications, pools, virtual hosts, or command-line processes with different fixed INI settings. With the `files` handler, this requires the same session storage directory, the same session ID, and permissions allowing both sides to access that file. Separate FPM pools do not automatically provide separate session storage. A runtime configuration change is not required, but workers using the same serializer do not create this mismatch.\r\n\r\nDuring multipart processing, PHP appends the submitted `PHP_SESSION_UPLOAD_PROGRESS` value to an upload-progress session key and persists it. The `php` format separates each key from its serialized value with `|`. The other formats represent keys differently. If their output is read as `php`, an attacker-supplied delimiter can cause bytes inside the key to be passed to PHP's unserialization machinery.\r\n\r\nObjects may be created and their deserialization or destruction callbacks invoked before trailing data causes the session decoder to reject the record. The 127-byte key limit in `php_binary` does not prevent payloads that span multiple session records.\r\n\r\n### Impact\r\n\r\nSuccessful exploitation can cause remote code execution, file modification, session corruption, or denial of service. The report includes command execution using a Guzzle object gadget on PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Command execution was also reproduced with a Monolog 2.11.1 gadget using a `php_serialize` writer and a `php` reader. Exploitability depends on the shared session configuration, access to the writing and reading paths, and the classes available to the reader.\r\n\r\nAn application that never changes its serializer at runtime can still be affected if another application or process writes incompatible data into the same se\n\nAffected packages: php:ext-session\nPatched: ext-session 8.2.36, ext-session 8.3.37, ext-session 8.4.28, ext-session 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx","published_at":"2026-11-19T14:08:31Z","updated_at":"2026-11-19T18:42:48Z","fetched_at":"2026-11-21T19:15:07.553369Z","severity":"critical","cvss_score":9.2,"epss":0.99999,"is_kev":true,"has_exploit":true,"kev_due_date":"2026-10-29","vendor":"php","product":"ext-session","vuln_id":"CVE-2026-115560","vuln_ids":["CVE-2026-109618","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-658J-R8RW-Q6MX","GHSA-6WMF-4RV5-P3RP","GHSA-W8HW-W9FX-J79W"],"tags":["repo-advisory","php","CWE-20","CWE-502","security","repo:php/php-src"],"cluster_id":458,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/631","html":"https://vulnwatch.ve1ve2.com/item/631"}},{"id":634,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-4646-p932-gw34 / CVE-2026-129506: SOAP use-after-free when processing DTD entity references","summary":"SOAP use-after-free when processing DTD entity references\n\n### Summary\r\n\r\nPHP's SOAP extension can read freed memory while processing XML containing a document type definition (DTD) and an entity reference in an attribute value. An unauthenticated attacker who can send a crafted request to an exposed SOAP endpoint can crash the PHP process handling it. Applications that load attacker-controlled WSDL or imported schema documents can also be affected.\r\n\r\n### Details\r\n\r\nWhile cleaning up a parsed XML document, PHP frees the DTD even though attribute values can still refer to content it owns. Processing those attributes can then access freed memory. Removing the DTD also bypasses the SOAP server's normal rejection of documents containing a DTD.\r\n\r\nThe fix keeps the DTD alive for as long as the XML document needs it and restores the existing SOAP DTD check. The issue predates the changes made for [CVE-2026-91765](https://github.com/php/php-src/security/advisories/GHSA-rgrp-mwpx-f6rm) and affects earlier releases in all supported PHP branches.\r\n\r\n### Impact\r\n\r\nExploitation requires the SOAP extension and an application that processes attacker-controlled SOAP XML, WSDL or schema content. Authentication does not protect an endpoint if the application parses the SOAP request before authenticating it.\r\n\r\nA crafted document can crash the PHP worker or process, and repeated requests can disrupt service. The original report also described corrupted type information after freed memory was reused. Disclosure of sensitive process memory and arbitrary code execution have not been confirmed.\r\n\r\n### Affected versions\r\n\r\nSOAP server requests have been affected since PHP 5.6.0. The same cleanup has applied to WSDL and schema documents since PHP 5.0.0, but loading an untrusted WSDL or schema is not considered a security issue. This is based on code inspection.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. Until then, restrict access to affected SOAP endpoints or disable them where practical. Load WSDL and imported schemas only from trusted, controlled sources.\r\n\r\nIf untrusted SOAP requests must be accepted, reject documents containing a DTD before they reach the SOAP extension. Any such filter must correctly handle the XML encodings and request-body transformations accepted by the application. A simple text search is not a complete mitigation.\r\n\n\nAffected packages: php:ext-soap\nPatched: ext-soap 8.2.36, ext-soap 8.3.37, ext-soap 8.4.28, ext-soap 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-4646-p932-gw34","published_at":"2026-11-19T14:08:23Z","updated_at":"2026-11-19T18:42:46Z","fetched_at":"2026-11-21T19:15:07.553372Z","severity":"high","cvss_score":7.5,"epss":0.01938,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2026-129506","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-4646-P932-GW34","GHSA-RGRP-MWPX-F6RM"],"tags":["repo-advisory","php","CWE-416","security","repo:php/php-src"],"cluster_id":461,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/634","html":"https://vulnwatch.ve1ve2.com/item/634"}},{"id":627,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-x8r7-mg3g-74hg / CVE-2026-129501: Double free during DOM XML serialization","summary":"Double free during DOM XML serialization\n\n### Summary\r\n\r\nPHP's modern DOM XML serializer can incorrectly share ownership of a generated namespace prefix between an element and its descendant. An application that calls `saveXml()` on attacker-controlled XML or HTML can consequently use and free the same allocation more than once, which can crash the PHP process.\r\n\r\n### Details\r\n\r\n`Dom\\XMLDocument` and `Dom\\HTMLDocument` maintain a namespace-prefix map while serializing a document as XML. The serializer can generate a prefix for an attribute whose namespace has no usable prefix. Descendants initially share the ancestor's map and use copy-on-write when adding another candidate prefix for an existing namespace URI.\r\n\r\nThe vulnerable copy-on-write path duplicates the candidate list but leaves the copied pointers marked as owned. Destroying the descendant's map therefore frees a generated prefix that remains referenced by the ancestor. A later sibling can access that freed value, and destroying the ancestor's map frees the same allocation again. The fix marks generated-prefix pointers copied into descendant lists as borrowed.\r\n\r\nValid input can establish this state by combining namespaced attributes, nested namespace declarations and a later sibling. The input does not need to be malformed. The HTML path requires only a crafted document followed by `Dom\\HTMLDocument::saveXml()`. For `Dom\\XMLDocument`, the same state can arise when ordinary application code adds a namespaced attribute and the supplied document declares another prefix for that namespace.\r\n\r\n### Impact\r\n\r\nA remote attack requires an application to parse attacker-controlled XML or HTML using the modern DOM API and then serialize it with `saveXml()`. Applications that do not XML-serialize untrusted documents are not affected by that attack path.\r\n\r\nThe demonstrated impact is memory corruption and denial of service through a PHP process crash. Corrupting ZendMM's free list may allow later allocations in the same request to alias, but turning that into type confusion or code execution requires application-specific allocation control and has not been demonstrated through realistic application code. No confidentiality or integrity impact has been established.\r\n\r\nRepeated requests can terminate PHP workers and reduce or exhaust an application's worker pool.\r\n\r\n### Affected versions\r\n\r\nThe affected code was introduced in PHP 8.4.0 together with the `Dom\\XMLDocument` and `Dom\\HTMLDocument` classes and their XML serializer. The legacy `DOMDocument` class does not use this serializer. PHP 8.3 and earlier are not affected.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. Until then, avoid calling `saveXml()` on attacker-controlled `Dom\\XMLDocument` or `Dom\\HTMLDocument` instances. For HTML documents where XML output is not required, `saveHtml()` avoids the affected XML serializer. Process isolation and worker restart limits can contain individual crashes but do not remove the vulnerable behavio\n\nAffected packages: php:ext-dom\nPatched: ext-dom 8.4.28, ext-dom 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-x8r7-mg3g-74hg","published_at":"2026-11-19T14:08:18Z","updated_at":"2026-11-19T19:01:04Z","fetched_at":"2026-11-21T19:15:07.553366Z","severity":"medium","cvss_score":6.3,"epss":0.0065,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-dom","vuln_id":"CVE-2026-129501","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-X8R7-MG3G-74HG"],"tags":["repo-advisory","php","CWE-415","CWE-416","security","repo:php/php-src"],"cluster_id":452,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/627","html":"https://vulnwatch.ve1ve2.com/item/627"}},{"id":639,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-q23r-hr55-xmpg / CVE-2026-15353: SOAP information disclosure through malformed array dimensions","summary":"SOAP information disclosure through malformed array dimensions\n\n### Summary\r\n\r\nPHP's SOAP extension can expose a small amount of uninitialized heap memory when processing an encoded array with an invalid `arraySize` value. An attacker can supply a crafted SOAP request or response that causes the decoded array to contain an unexpected integer key. The value reaches the attacker if the application returns or otherwise exposes that array.\r\n\r\n### Details\r\n\r\nAn empty, whitespace-only or non-numeric `arraySize` can describe no dimensions. PHP nevertheless reads the first array position, which has not been initialized. With PHP's default memory allocator, the read falls within a small allocated block and can return four bytes of unrelated heap data. That value is then used as an array key. When the default allocator is disabled, AddressSanitizer reports an out-of-bounds heap read.\r\n\r\nThe fix treats a size containing no dimensions as a one-dimensional array. It also covers array dimensions read from WSDL definitions. The vulnerable behaviour is present in all supported PHP branches.\r\n\r\n### Impact\r\n\r\nAn unauthenticated client can trigger the issue through a SOAP endpoint that accepts the crafted input. A malicious or compromised SOAP server can also supply an affected response to `SoapClient`.\r\n\r\nThe demonstrated impact is limited information disclosure when the application exposes the decoded array. Simply accepting the request does not guarantee that the value is returned to the attacker. The demonstrated case does not crash or corrupt memory with PHP's default allocator. Arbitrary code execution has not been demonstrated.\r\n\r\n### Affected versions\r\n\r\nThe affected code has been present since PHP 5.0.0. This is based on code inspection.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. Until then, restrict access to affected SOAP endpoints and use trusted SOAP services and WSDL definitions.\r\n\r\nWhere requests or responses can be validated before they reach the SOAP extension, reject encoded arrays whose `arraySize` contains no valid dimension. Avoid returning unvalidated decoded arrays to untrusted clients. These measures reduce exposure but do not replace the parser fix.\r\n\n\nAffected packages: php:ext-soap\nPatched: ext-soap 8.2.36, ext-soap 8.3.37, ext-soap 8.4.28, ext-soap 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-q23r-hr55-xmpg","published_at":"2026-11-19T14:08:10Z","updated_at":"2026-11-19T18:42:42Z","fetched_at":"2026-11-21T19:15:07.553375Z","severity":"medium","cvss_score":6.3,"epss":0.00839,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2026-15353","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-Q23R-HR55-XMPG"],"tags":["repo-advisory","php","CWE-125","CWE-908","security","repo:php/php-src"],"cluster_id":469,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/639","html":"https://vulnwatch.ve1ve2.com/item/639"}},{"id":638,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-68fq-fh7h-f8gr / CVE-2026-128090: PHAR OpenSSL signature bypass via algorithm downgrade","summary":"PHAR OpenSSL signature bypass via algorithm downgrade\n\n### Summary\n\nAn attacker who can modify an OpenSSL-signed Phar archive without changing its trusted public key can make PHP accept arbitrary archive contents. The attacker changes the archive's signature type to a keyless hash such as SHA-256 and replaces the OpenSSL signature with a matching digest. Applications that execute the archive may then run attacker-controlled PHP code.\n\n### Details\n\nPHP stores an OpenSSL signature in the Phar archive, but obtains the verification key from a separate `\n.pubkey` file. For the native phar format, the archive controls the signature type through the four bytes before the `GBMB` magic. Tar- and zip-based phars control it through the first four bytes of `.phar/signature.bin`.\n\nThe verifier treats this type as authoritative when selecting the verification method. Only the OpenSSL signature types read and use `\n.pubkey`. MD5, SHA-1, SHA-256 and SHA-512 compare a digest that anyone can recompute. An attacker can therefore replace the archive contents and OpenSSL signature, select SHA-256 and satisfy `phar.require_hash=1` without possession of the private key. The trusted public key is not consulted.\n\nNative, tar- and zip-based executable phars are affected. Explicitly signed tar- and zip-based `PharData` archives use the same verification path. This behaviour has been present since OpenSSL Phar signatures were introduced in PHP 5.3.0. The fix rejects a non-OpenSSL signature when an adjacent `.pubkey` file indicates that OpenSSL verification is expected. Archives without such a sidecar retain their existing signature behaviour.\n\n### Impact\n\nExploitation requires the application to rely on an OpenSSL-signed Phar with a public key installed through a trusted channel, an attacker able to alter or replace the archive but not that public key, and the application subsequently loading the archive. Executing the modified archive can run attacker-controlled PHP code with the privileges of the affected process, compromising its data and availability.\n\nThe `.pubkey` file is PHP's external trust anchor and is not embedded or pinned in the Phar. If an attacker can also remove or replace it, they can already provide an archive signed with their own OpenSSL key. the fix does not protect that deployment. `phar.require_hash` alone provides corruption detection and does not authenticate keyless signatures.\n\n### Affected versions\n\nThe affected code has been present since PHP 5.3.0. This is based on code inspection.\n\n### Mitigation\n\nUpgrade to the fixed release for your PHP branch when it becomes available. Obtain the publisher's public key through an authenticated channel and install it as `\n.pubkey` with permissions that prevent the archive update or download path from removing or replacing it. If the key cannot be protected independently, verify the archive using another mechanism that pins a trusted key before PHP loads it.\n\nAffected packages: php:ext-phar\nPatched: ext-phar 8.2.36, ext-phar 8.3.37, ext-phar 8.4.28, ext-phar 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-68fq-fh7h-f8gr","published_at":"2026-11-19T14:08:01Z","updated_at":"2026-11-19T18:42:43Z","fetched_at":"2026-11-21T19:15:07.553375Z","severity":"high","cvss_score":7.7,"epss":0.00318,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-phar","vuln_id":"CVE-2026-128090","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-68FQ-FH7H-F8GR"],"tags":["repo-advisory","php","CWE-347","CWE-757","security","repo:php/php-src"],"cluster_id":468,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/638","html":"https://vulnwatch.ve1ve2.com/item/638"}},{"id":637,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-5j3f-64r7-f564 / CVE-2026-129538: PHP-CGI out-of-bounds read and write during PATH_INFO correction","summary":"PHP-CGI out-of-bounds read and write during PATH_INFO correction\n\n### Summary\n\nThe PHP CGI binary (`php-cgi`) can access memory outside the supplied path information when a web server passes inconsistent script and path values. Depending on the request and configuration, an unauthenticated attacker may be able to crash the PHP process, expose process memory, or corrupt memory.\n\nThis affects `php-cgi` in both CGI and FastCGI mode when `cgi.fix_pathinfo=1`, the default. PHP-FPM and PHP running as an Apache module are not affected.\n\n### Details\n\nThe problem occurs when PHP removes a trailing path from `SCRIPT_FILENAME`, or from `PATH_TRANSLATED` in a redirected CGI request, but the supplied `PATH_INFO` is shorter than the path being removed. A present but empty `PATH_INFO` can also trigger the problem. This requires particular web server mappings; using CGI, FastCGI, or URL rewriting alone is not enough.\n\nIn `init_request_info()`, PHP calculates the replacement `PATH_INFO` by subtracting the length of the removed suffix from the end of the supplied value. If the suffix is longer, the resulting pointer lies before the `PATH_INFO` buffer. Subsequent path correction can read, write and copy memory through this invalid pointer. The fix checks the lengths before deriving the pointer and skips the rewrite when no valid replacement exists.\n\n#### Apache CGI example\n\nA legitimate configuration that can produce these values is a legacy Apache CGI installation using `Action`, combined with a rewrite to an absolute filesystem path. For example, this virtual-host configuration routes a short public URL to a longer route handled by an existing `/srv/site/index.php`:\n\n```apache\nDocumentRoot \"/srv/site\"\nScriptAlias /cgi-bin/php \"/usr/local/bin/php-cgi\"\n\nAddHandler php-script .php\nAction php-script /cgi-bin/php\n\nAcceptPathInfo On\n\nRewriteEngine On\nRewriteRule \"^/news/(.*)$\" \"/srv/site/index.php/content/articles/$1\" [L]\n```\n\nThis fragment assumes an otherwise working Apache CGI installation with the required modules and access permissions. The `Action` arrangement is described in the [PHP CGI installation documentation](https://www.php.net/manual/en/security.cgi-bin.force-redirect.php).\n\nA request for `/news/x` can then reach PHP with:\n\n```text\nPATH_INFO = /news/x\nPATH_TRANSLATED = /srv/site/index.php/content/articles/x\nREDIRECT_URL = /news/x\n```\n\nPHP finds the existing `index.php`, but the remaining `/content/articles/x` is longer than the original `/news/x`. Attempting to reconcile these values triggers the invalid memory access. This was reproduced through an actual HTTP request with Apache 2.4.58 and an unmodified PHP CGI binary. An `Alias` that maps `/news` to `/srv/site/index.php/content/articles` produced the same result.\n\nThe ordinary `Action` setup, a conventional rewrite to `index.php`, and a rewrite to the URL `/index.php/content/articles/x` did not trigger the issue in these tests. The vulnerable example is a valid routing confi\n\nAffected packages: php:sapi-cgi\nPatched: sapi-cgi 8.2.36, sapi-cgi 8.3.37, sapi-cgi 8.4.28, sapi-cgi 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-5j3f-64r7-f564","published_at":"2026-11-19T14:07:53Z","updated_at":"2026-11-19T18:42:43Z","fetched_at":"2026-11-21T19:15:07.553374Z","severity":"medium","cvss_score":6.9,"epss":0.12818,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"sapi-cgi","vuln_id":"CVE-2026-129538","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129474","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-2FJV-P558-G82M","GHSA-5J3F-64R7-F564","GHSA-8MJJ-2R7P-4HG2"],"tags":["repo-advisory","php","CWE-125","CWE-787","CWE-823","security","repo:php/php-src"],"cluster_id":467,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/637","html":"https://vulnwatch.ve1ve2.com/item/637"}},{"id":636,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-3mg3-cr28-46gc / CVE-2026-129292: PHP-FPM status endpoint XSS via unescaped user and script fields","summary":"PHP-FPM status endpoint XSS via unescaped user and script fields\n\n### Summary\r\n\r\nPHP-FPM can include attacker-controlled request metadata without escaping it in the full status response. An unauthenticated attacker can place HTML or JavaScript in a worker's scoreboard entry and execute it in the browser of an operator who later views the full HTML status page. The attacker does not need access to the status endpoint.\r\n\r\n### Details\r\n\r\nThe earlier fix for [CVE-2026-6735](https://github.com/php/php-src/security/advisories/GHSA-7qg2-v9fj-4mwv) escaped the request URI and query string, but left the request method, authentication user and script filename unescaped in the per-process status output. These values are stored in the PHP-FPM scoreboard and later inserted into HTML, XML and JSON responses without the encoding required by each format.\r\n\r\nThe most direct attack uses the username from an HTTP Basic authentication header. When the front end forwards this header to PHP-FPM, PHP can decode and store the supplied username even if the application does not use Basic authentication. The scoreboard retains up to 31 bytes of the username, which is enough for an HTML element with a JavaScript event handler. A request to an ordinary PHP script in the pool can therefore plant a payload that runs when another user opens the status endpoint with `full&html`. The value remains in that worker's scoreboard entry until it is replaced by a later request.\r\n\r\nThe script filename provides another injection path when an attacker can influence the filename recorded by FPM, including configurations using `cgi.fix_pathinfo=0`. Ordinary web servers restrict the characters accepted in request methods, so the request-method field does not by itself establish the same HTTP attack path. Unescaped quotes or markup in these fields can also corrupt JSON or XML status responses and interfere with monitoring consumers.\r\n\r\nThe fix applies a common, format-appropriate escaping helper to the request method, request URI, query string, authentication user and script filename before rendering the full status response. A separate client-side injection issue in the bundled `status.html` dashboard is tracked in [GHSA-q8fm-p8fx-h6r6](https://github.com/php/php-src/security/advisories/GHSA-q8fm-p8fx-h6r6).\r\n\r\n### Impact\r\n\r\nExploitation requires an enabled PHP-FPM status endpoint, a request path through which attacker-controlled metadata reaches the affected pool, and a user or tool that renders the full status data as HTML. For the authentication-user attack, the front end must forward the Basic authentication header to FPM. Restricting access to the status endpoint does not prevent an attacker from planting the payload through a separate application request.\r\n\r\nSuccessful exploitation runs JavaScript in the status page's origin. It can expose request URIs, query strings and other information shown on the status page. If the page shares an origin with the application, the script can also act with the viewing user's session and read data available to that \n\nAffected packages: php:sapi-fpm\nPatched: sapi-fpm 8.2.36, sapi-fpm 8.3.37, sapi-fpm 8.4.28, sapi-fpm 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-3mg3-cr28-46gc","published_at":"2026-11-19T14:07:47Z","updated_at":"2026-11-19T18:42:44Z","fetched_at":"2026-11-21T19:15:07.553373Z","severity":"high","cvss_score":7.6,"epss":0.0107,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"sapi-fpm","vuln_id":"CVE-2026-129292","vuln_ids":["CVE-2025-14179","CVE-2026-115560","CVE-2026-12184","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-3MG3-CR28-46GC","GHSA-7QG2-V9FJ-4MWV","GHSA-Q8FM-P8FX-H6R6"],"tags":["repo-advisory","php","CWE-79","security","repo:php/php-src"],"cluster_id":464,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/636","html":"https://vulnwatch.ve1ve2.com/item/636"}},{"id":632,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-gr4f-wgx5-jpfv / CVE-2026-129496: Timezone cache use-after-free can lead to remote code execution","summary":"Timezone cache use-after-free can lead to remote code execution\n\n### Summary\r\n\r\nPHP can retain a reference to a freed timezone cache when a diagnostic is written to a PHP error log file during process startup. A later diagnostic during early request initialization can access the freed cache before it is reset. On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker.\r\n\r\n### Details\r\n\r\nPHP formats file-based error log timestamps using the configured timezone. In a non-thread-safe build, a diagnostic emitted during module startup can cause PHP to allocate the timezone cache in temporary startup memory. That memory is released at the end of startup, but the internal reference to the cache remains until the date extension initializes the first request. An earlier diagnostic, such as the warning produced when request input exceeds `max_input_vars`, can therefore read or modify a freed hash table. The released memory may already contain attacker-controlled request data.\r\n\r\nThe startup diagnostic must occur late enough that subsequent initialization does not clear the cached reference. Confirmed examples include an invalid `date.timezone` value and a warning or deprecation caused by session configuration. The diagnostic must actually be written through PHP's file-based `error_log` path. FPM's own error log does not by itself meet this condition.\r\n\r\nIn FPM and Apache mod_php, workers can inherit the stale reference from the parent process. The vulnerable window lasts until a worker completes its first normal request. Newly created or recycled workers can encounter the same condition. A crafted HTTP request has been shown to crash an FPM worker using the default `max_input_vars` value and ordinary nginx header limits. The issue has also been reproduced with CGI.\r\n\r\nA separate local FPM proof demonstrated native command execution with known runtime addresses. It uses early HTTP Basic credential decoding to replace the stale cache, then reuses request-data allocations and triggers their destruction while `$_REQUEST` is constructed. That particular chain requires additional configuration, including `auto_globals_jit=0` and cookies in `request_order`, a suitable heap layout, and an Authorization header larger than nginx's default per-header limit. These are conditions of the demonstrated exploit, not general requirements of the underlying memory-corruption flaw. Other exploitation paths may be possible.\r\n\r\nNative command execution has also been demonstrated in Apache mod_php. Besides the same GET/COOKIE chain, Apache has a separate path when request startup fails before the cache is reset. Request cleanup can destroy the forged cache and invoke an attacker-controlled destructor. The demonstrated variant uses a POST that exceeds a configured 2 MB PHP memory limit and requires known runtime addresses, a suitable heap layout, and a larger allowed Authorization header. It does not require cookies or changes\n\nAffected packages: php:ext-date\nPatched: ext-date 8.2.36, ext-date 8.3.37, ext-date 8.4.28, ext-date 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv","published_at":"2026-11-19T14:06:44Z","updated_at":"2026-11-19T18:42:47Z","fetched_at":"2026-11-21T19:15:07.553370Z","severity":"critical","cvss_score":9.2,"epss":0.08139,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-date","vuln_id":"CVE-2026-129496","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-GR4F-WGX5-JPFV"],"tags":["repo-advisory","php","CWE-416","CWE-459","security","repo:php/php-src"],"cluster_id":459,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/632","html":"https://vulnwatch.ve1ve2.com/item/632"}},{"id":633,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-fm2m-fjf5-v3cp / CVE-2026-126714: Partially overwritten session files can lead to remote code execution","summary":"Partially overwritten session files can lead to remote code execution\n\n### Summary\r\n\r\nPHP's file-based session handler can leave a session file containing parts of two different serialized sessions if a write is interrupted. An attacker who can influence the session contents and interrupt a replacement write may be able to make PHP deserialize attacker-controlled objects when the session is next opened. A suitable object gadget chain in the application can turn this into remote code execution.\r\n\r\nThis affects the `files` session save handler, which is PHP's default. The issue is not limited to session upload progress or PHP 8.6.\r\n\r\n### Details\r\n\r\nWhen updating a session, `ps_files_write()` writes the new serialized data into the existing file. The vulnerable implementation does not clear the existing contents before every write. If the operation stops after replacing only part of the file, the result can contain a prefix of the new session followed by a suffix of the old one. The file lock prevents competing session operations from accessing the file during the write, but does not make an interrupted write atomic.\r\n\r\nPHP's session decoders use its unserialization machinery to restore session values. Carefully arranged old and new data can cause the combined file to be interpreted differently from either original session. Bytes that were previously part of an ordinary string can become serialized object data. A later `session_start()` or another session-reading operation can then create those objects and invoke their deserialization behavior.\r\n\r\nSession upload progress provides one way for a remote client to influence stored session data through multipart uploads. The same underlying problem can arise when an application stores large user-controlled strings in a session. In threaded PHP builds, a hard memory-limit failure in another thread can terminate the process while the session write is in progress. This provides a way to influence where the write stops.\r\n\r\nThe fix truncates the session file to zero before writing the replacement data and aborts the write if truncation fails. An interrupted write can still lose session data, but it can no longer retain the old suffix that enables this attack.\r\n\r\n### Impact\r\n\r\nSuccessful exploitation can execute code with the privileges of the PHP worker. It requires attacker influence over the session data, an interruption at a useful point in the write, and an application with a suitable deserialization gadget chain. The issue can also corrupt session state. Authentication requirements depend on how the application exposes the affected session operations.\r\n\r\nOther session storage implementations are not affected by this specific file-write defect, although their own handling of interrupted updates must be considered separately.\r\n\r\n### Affected versions\r\n\r\nThe affected code has been present since PHP 4.1.0. This is based on code inspection.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. As a temporary measure, disable `session.up\n\nAffected packages: php:ext-session\nPatched: ext-session 8.2.36, ext-session 8.3.37, ext-session 8.4.28, ext-session 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp","published_at":"2026-11-19T14:06:39Z","updated_at":"2026-11-19T18:42:47Z","fetched_at":"2026-11-21T19:15:07.553371Z","severity":"critical","cvss_score":9.2,"epss":0.13104,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-session","vuln_id":"CVE-2026-126714","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-FM2M-FJF5-V3CP"],"tags":["repo-advisory","php","CWE-367","CWE-662","security","repo:php/php-src"],"cluster_id":460,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/633","html":"https://vulnwatch.ve1ve2.com/item/633"}},{"id":623,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-8mjj-2r7p-4hg2 / CVE-2026-129474: Use-after-free in magic method backtraces can lead to remote code execution","summary":"Use-after-free in magic method backtraces can lead to remote code execution\n\n### Summary\r\n\r\nPHP can access freed memory when collecting the arguments of a method handled by `__call()` or `__callStatic()` for a backtrace. On PHP 8.5 and later, an unauthenticated attacker may be able to trigger this through a crafted request that causes a fatal error while the application enters such a method. Successful exploitation can execute arbitrary code with the privileges of the PHP worker.\r\n\r\nThe demonstrated remote attack requires `fatal_error_backtraces=1` and `zend.exception_ignore_args=0`. Fatal error backtraces are enabled by default in PHP 8.5. PHP's built-in default also includes arguments, but `php.ini-production` sets `zend.exception_ignore_args=1` and prevents this attack path.\r\n\r\n### Details\r\n\r\nApplications and frameworks commonly use `__call()` and `__callStatic()` to forward method calls to another object, including logging facades, database interfaces and service proxies. Before PHP enters the actual magic method, it briefly represents the requested method as a separate call. A backtrace taken during this interval can collect values left behind by an earlier call instead of the current arguments. Some of those values can refer to memory that has already been freed.\r\n\r\nThe demonstrated attack submits crafted JSON to an import endpoint that processes the body and then logs it through a magic static method. The request is sized so that constructing a logging argument crosses `memory_limit`. PHP 8.5.12 introduced delayed handling of this allocation failure, allowing the fatal error to be reported while the magic method call is being entered. If fatal error backtraces include arguments, PHP can then treat request-controlled bytes in reused memory as live values. Processing or releasing the backtrace can corrupt memory or transfer control to an attacker-chosen address.\r\n\r\nFatal error backtraces were introduced in PHP 8.5.0. An execution time limit expiring during the same interval is another possible trigger. PHP 8.2–8.4 contain the underlying backtrace error, but reaching it requires a PCNTL signal handler or another component to inspect an interrupted call. No attacker-controlled remote trigger has been established for those branches. They are therefore outside this advisory’s affected version range.\r\n\r\n### Impact\r\n\r\nRemote code execution has been confirmed on PHP 8.5 and later. Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point. The demonstrated code execution chain also requires knowledge of usable memory addresses despite address space randomisation. Other attempts can crash the worker or produce an ordinary resource limit error.\r\n\r\nPotentially relevant paths include [Laravel facades](https://github.com/laravel/framework/blob/v13.40.0/src/Illuminate/Support/Facades/Facade.php#L356) and [Magento guest shipping estimation](https://github.com/magento/magento2/blob/2.4.9/app/code/Magento\n\nAffected packages: php:engine\nPatched: engine 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2","published_at":"2026-11-19T14:06:20Z","updated_at":"2026-11-19T19:04:50Z","fetched_at":"2026-11-21T19:15:07.553360Z","severity":"critical","cvss_score":9.2,"epss":0.07248,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"engine","vuln_id":"CVE-2026-129474","vuln_ids":["CVE-2026-129474","CVE-2026-129538","GHSA-2FJV-P558-G82M","GHSA-5J3F-64R7-F564","GHSA-8MJJ-2R7P-4HG2"],"tags":["repo-advisory","php","CWE-416","security","repo:php/php-src"],"cluster_id":444,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/623","html":"https://vulnwatch.ve1ve2.com/item/623"}},{"id":625,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-mg3p-mxj9-g2mm / CVE-2026-129438: Incorrect RFC 3986 URI serialization for oversized input","summary":"Incorrect RFC 3986 URI serialization for oversized input\n\n### Summary\r\n\r\nPHP's RFC 3986 URI implementation can return an incorrect string when a very large URI is converted back to text. An application that accepts attacker-controlled URI data and has enough memory to process it may receive a truncated or invalid URI instead of an error. Processing these inputs can also exhaust memory or terminate the PHP process.\r\n\r\nThis affects the `Uri\\Rfc3986\\Uri` class introduced in PHP 8.5.0. The legacy `parse_url()` function and the separate `Uri\\WhatWg\\Url` implementation are not affected by this issue.\r\n\r\n### Details\r\n\r\nPHP uses the uriparser library to convert an RFC 3986 URI back to text. The vulnerable implementation does not correctly handle the library's output-size limit or errors returned while calculating or writing the result.\r\n\r\nFor a URI whose string representation is exactly 2,147,483,647 bytes, PHP overflows the size calculation when it reserves space for the terminating byte. The conversion then fails, but PHP can still return the allocated string as a successful result. With longer URIs, PHP can use an incomplete length calculation and return only part of the URI.\r\n\r\nTesting on a normal, non-debug PHP build confirmed that `toString()` and `toRawString()` could return a 2,147,483,647-byte string containing zeroes. A URI one byte longer returned only its `a://b/` prefix. Other operations that convert an RFC 3986 URI to text can reach the same implementation.\r\n\r\nThe defect is in PHP's handling of uriparser's size limit and return values. Updating uriparser alone does not correct it. Correct handling requires PHP to reject a representation that cannot fit the library's supported output size and report a conversion error instead of returning an invalid string.\r\n\r\n### Impact\r\n\r\nExploitation requires an application to pass attacker-controlled URI data large enough to reach the approximately 2 GiB boundary to an affected operation. The PHP process must also have enough memory to construct and process the URI. Normal application-level URI length limits prevent the demonstrated inputs from reaching this condition.\r\n\r\nAn application that trusts the resulting string may make an incorrect comparison, validation or routing decision, or store an incomplete URI. The large allocations can also exhaust the request's memory allowance. In the tested development build, exceeding the soft memory limit produced a memory-exhaustion error; exceeding the hard limit immediately terminated the PHP process. This can temporarily reduce service capacity.\r\n\r\nThe allocations remain subject to PHP's memory-limit checks. A memory-limit bypass was not observed. The tests also did not establish disclosure of data from other requests: the large result allocation used fresh operating-system memory and contained zeroes. Arbitrary code execution and broader confidentiality or integrity impact have not been demonstrated.\r\n\r\n### Affected versions\r\n\r\nThe affected code was introduced in PHP 8.5.0 together with the `Uri\\Rfc3986\\Uri` class. P\n\nAffected packages: php:ext-uri\nPatched: ext-uri 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-mg3p-mxj9-g2mm","published_at":"2026-11-19T14:06:16Z","updated_at":"2026-11-19T19:01:06Z","fetched_at":"2026-11-21T19:15:07.553364Z","severity":"medium","cvss_score":6.3,"epss":0.00562,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-uri","vuln_id":"CVE-2026-129438","vuln_ids":["CVE-2026-129438","GHSA-MG3P-MXJ9-G2MM"],"tags":["repo-advisory","php","CWE-190","CWE-252","security","repo:php/php-src"],"cluster_id":448,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/625","html":"https://vulnwatch.ve1ve2.com/item/625"}},{"id":630,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-f6gg-rchx-xw8j / CVE-2026-128064: Mixed-case HTTPS and FTPS URLs can expose data in plaintext","summary":"Mixed-case HTTPS and FTPS URLs can expose data in plaintext\n\n### Summary\r\n\r\nPHP's HTTP and FTP stream wrappers can send data without encryption when an HTTPS or FTPS URL has an uppercase `S` in its scheme, for example `HTTPS://`, `httpS://` or `FTPS://`. Applications using `file_get_contents()`, `fopen()` or other stream functions may therefore expose passwords, authentication tokens, request bodies or transferred files to an attacker able to observe the network traffic.\r\n\r\n### Details\r\n\r\nThe stream wrappers recognise URL schemes without regard to case, but the decision to enable TLS checks for a lowercase `s` at a fixed position. A URL that passes an application's case-insensitive HTTPS or FTPS validation can consequently use the unencrypted HTTP or FTP transport.\r\n\r\nThe HTTP issue also applies to redirect targets. For example, a `307` redirect from a valid HTTPS connection to an uppercase `HTTPS://` URL can cause the preserved POST body and any retained authentication headers to be sent in cleartext. A request can disclose data even if the destination rejects the unexpected plaintext connection.\r\n\r\nThe fix determines whether TLS is required by comparing the complete scheme case-insensitively. It covers both the HTTP and FTP stream wrappers.\r\n\r\n### Impact\r\n\r\nAn attacker who can observe an affected connection can read the data that the application expected TLS to protect. This can include Basic authentication credentials, bearer tokens, cookies, sensitive POST data, FTP login credentials and file contents. Exploitation requires an affected URL to reach a stream wrapper, either directly or through a redirect, and access to the resulting network traffic. The impact depends on the data being transferred. disclosure of credentials or other highly sensitive data can have a serious confidentiality impact.\r\n\r\n### Affected versions\r\n\r\nMixed-case URLs passed by an application have been affected since PHP 5.2.0, and redirects to a mixed-case URL since PHP 4.3.0. This is based on code inspection.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. As a temporary workaround, ensure that HTTPS and FTPS URL schemes are written in lowercase before passing them to a stream function. If HTTP redirects are allowed, disable automatic redirects and validate and normalise every redirect target before following it. Normalising only the initial URL does not protect requests that follow redirects automatically.\r\n\n\nAffected packages: php:ext-standard\nPatched: ext-standard 8.2.36, ext-standard 8.3.37, ext-standard 8.4.28, ext-standard 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-f6gg-rchx-xw8j","published_at":"2026-11-19T14:06:12Z","updated_at":"2026-11-19T18:42:49Z","fetched_at":"2026-11-21T19:15:07.553368Z","severity":"high","cvss_score":8.2,"epss":0.00273,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-standard","vuln_id":"CVE-2026-128064","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-F6GG-RCHX-XW8J"],"tags":["repo-advisory","php","CWE-319","security","repo:php/php-src"],"cluster_id":457,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/630","html":"https://vulnwatch.ve1ve2.com/item/630"}},{"id":629,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-mmf9-xm3v-hg2x / CVE-2026-127960: Denial of service through folded HTTP response headers","summary":"Denial of service through folded HTTP response headers\n\n### Summary\r\n\r\nA malicious HTTP server can cause PHP's built-in HTTP stream wrapper to consume excessive CPU while reading a response. Applications using `file_get_contents()`, `fopen()` or other stream functions to fetch an HTTP or HTTPS URL may become slow or unavailable if the response contains a header split across a large number of continuation lines.\r\n\r\n### Details\r\n\r\nWhen PHP receives a folded response header, it joins each continuation line to the accumulated header value. The vulnerable implementation allocates a new string and copies the entire value for every line. A response containing many short continuation lines therefore takes disproportionately more time to process as its size grows. PHP performs this work before returning the response body to the application.\r\n\r\nThis behaviour was introduced by the fix for GHSA-v8xr-gpvj-cx9g (CVE-2025-1217). The new fix accumulates the header in a growing buffer, avoiding a full copy for every continuation line while preserving the existing handling of folded headers.\r\n\r\n### Impact\r\n\r\nAn attacker must control an HTTP response fetched by the application through PHP's built-in HTTP or HTTPS stream wrapper. Enabling `allow_url_fopen` alone does not make an application vulnerable to a remote attack. the attacker must also be able to trigger a suitable outbound request or influence a server that the application already contacts.\r\n\r\nRepeated or concurrent requests can keep PHP workers busy and deny service to other users. Testing confirmed that two malicious responses could occupy both workers in a two-worker PHP-FPM pool and temporarily prevent an unrelated request from completing. The demonstrated impact is denial of service through excessive CPU consumption. No confidentiality or integrity impact was observed.\r\n\r\n### Affected versions\r\n\r\nThe affected code was introduced by the fix for GHSA-v8xr-gpvj-cx9g, first released in PHP 8.1.32, 8.2.28, 8.3.19 and 8.4.5. Earlier versions are not affected.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. Until then, restrict outbound requests to trusted destinations, including redirect targets. An egress proxy that enforces response-header size and count limits can reject malicious responses before PHP processes them. Request execution limits and PHP-FPM's `request_terminate_timeout` can limit how long workers remain occupied, but do not remove the vulnerable parsing behaviour.\r\n\n\nAffected packages: php:ext-standard\nPatched: ext-standard None, ext-standard 8.2.36, ext-standard 8.3.37, ext-standard 8.4.28, ext-standard 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-mmf9-xm3v-hg2x","published_at":"2026-11-19T14:06:08Z","updated_at":"2026-11-19T18:51:52Z","fetched_at":"2026-11-21T19:15:07.553367Z","severity":"high","cvss_score":8.7,"epss":0.00585,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-standard","vuln_id":"CVE-2026-127960","vuln_ids":["CVE-2025-1217","CVE-2025-1219","CVE-2025-1734","CVE-2025-1736","CVE-2025-1861","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-MMF9-XM3V-HG2X","GHSA-V8XR-GPVJ-CX9G"],"tags":["repo-advisory","php","CWE-400","CWE-407","security","repo:php/php-src"],"cluster_id":455,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/629","html":"https://vulnwatch.ve1ve2.com/item/629"}},{"id":624,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-2fjv-p558-g82m / CVE-2026-129182: Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown","summary":"Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown\n\n### Summary\r\n\r\nAs part of CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp), PHP 8.5.12 fixes a generic use-after-free of the `last_fatal_error_backtrace` global by clearing it during executor shutdown. Further scenarios have been discovered in which a fatal diagnostic during later shutdown work repopulates the global. The request heap is then released, and an early diagnostic in a subsequent request handled by the same worker can access the stale backtrace before normal executor initialization.\r\n\r\n### Details\r\n\r\nThe backtrace can be recreated while PHP restores modified INI settings after executor cleanup:\r\n\r\n- When `max_memory_limit` is specified in both the global and a path-specific configuration, restoring the global limit can fail if memory consumption still exceeds that limit. The resulting fatal error recreates the backtrace.\r\n- When the global configuration specifies `zlib.output_compression=1`, and a path-specific configuration specifies `zlib.output_compression=0` and `output_handler=ob_gzhandler` (or another handler), restoring compression before restoring `output_handler` can raise a fatal configuration error because the two settings conflict.\r\n\r\nBoth shutdown cases are possible with PHP-FPM and mod_php. The `max_memory_limit` override requires administrative configuration. `.user.ini` can supply the zlib settings but cannot change `max_memory_limit`.\r\n\r\nExploitation also requires a diagnostic before executor initialization in a later request handled by the same worker. Apache per-directory configuration can provide this. FPM is conditionally exposed when the frontend sends a diagnostic-producing `PHP_VALUE` or `PHP_ADMIN_VALUE` FastCGI parameter. Ordinary FPM pool settings and `.user.ini` do not provide this early diagnostic.\r\n\r\nThe fix is generic: PHP no longer creates or consumes the fatal-error backtrace while the executor is inactive. This also covers other shutdown diagnostics that might recreate the same state.\r\n\r\n### Impact\r\n\r\nSuccessful exploitation can result in memory corruption and potentially full remote code execution (RCE), as in CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp). The two restoration cases demonstrate heap use-after-free and worker crashes. RCE through these specific entry points has not been demonstrated.\r\n\r\n### Affected versions\r\n\r\nThe affected global was introduced in PHP 8.5.0 by fatal error backtraces. The fix for CVE-2026-109619 in PHP 8.5.12 cleared it during executor shutdown but did not stop later shutdown work from setting it again, so every PHP 8.5 release before 8.5.13 is affected. PHP 8.4 and earlier do not contain the global and are not affected.\r\n\r\n### Mitigation\r\n\r\nUpgrade to PHP 8.5.13 when it becomes available. As a temporary workaround, disable fatal-error backtraces administratively with `fatal_error_backtraces=0` and restart all workers. Ensure that request-specific configuration cannot re-enable the setting.\r\n\n\nAffected packages: php:engine\nPatched: engine 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m","published_at":"2026-11-19T14:06:04Z","updated_at":"2026-11-19T19:01:07Z","fetched_at":"2026-11-21T19:15:07.553363Z","severity":"critical","cvss_score":9.2,"epss":0.99999,"is_kev":true,"has_exploit":true,"kev_due_date":"2026-10-29","vendor":"php","product":"engine","vuln_id":"CVE-2026-129182","vuln_ids":["CVE-2026-109618","CVE-2026-109619","CVE-2026-129182","CVE-2026-129474","CVE-2026-129538","GHSA-2FJV-P558-G82M","GHSA-5J3F-64R7-F564","GHSA-6WMF-4RV5-P3RP","GHSA-8MJJ-2R7P-4HG2","GHSA-W8HW-W9FX-J79W"],"tags":["repo-advisory","php","CWE-416","CWE-459","security","repo:php/php-src"],"cluster_id":446,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/624","html":"https://vulnwatch.ve1ve2.com/item/624"}},{"id":626,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-g3vh-838c-65v7 / CVE-2026-129481: Use-after-free after interrupted session shutdown","summary":"Use-after-free after interrupted session shutdown\n\n### Summary\r\n\r\nPHP can retain a pointer to a script filename after session shutdown is interrupted and the request memory has been released. A later request handled by the same worker can then release the stale string, causing a heap use-after-free.\r\n\r\nThis is an incomplete fix for CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp). It affects PHP 8.3 and later. PHP 8.2 does not contain the affected session filename field.\r\n\r\n### Details\r\n\r\nWhen a session starts, PHP records the executing script's filename in an internal global variable. Session shutdown normally releases this string, but it destroys the session variables first. That destruction can invoke application callbacks, including a user-defined stream wrapper's `stream_close()` method.\r\n\r\nA fatal error in such a callback can abort session shutdown before the filename is released or cleared. PHP catches the bailout and continues shutting down the request. The request heap is then freed while the worker still retains the filename pointer.\r\n\r\nThe next request's session initialization does not reset this field. Starting another session can release the stale string, and ordinary session-module shutdown can also reach it even when the next script does not call any session functions. The requests must reach the same worker, but they do not need to belong to the same user or session.\r\n\r\nThe reported reproducer uses PHP-FPM with OPcache disabled and a stream resource held in the session. Its close callback raises a fatal error during cleanup. A subsequent request then reaches the freed filename. The report confirms the use-after-free on PHP 8.4.27 and 8.5.12. PHP 8.3.36 contains the same vulnerable code.\r\n\r\nUnlike the early-error and upload-progress cases in the original advisory, this path does not require a diagnostic-producing FastCGI parameter or session upload progress.\r\n\r\n### Impact\r\n\r\nAn attacker who can cause an application's session cleanup to fail in this way may corrupt memory or crash a reused PHP worker. The use-after-free could potentially lead to remote code execution, but code execution through this specific field has not been demonstrated. Authentication requirements depend on the application path that reaches the failing cleanup.\r\n\r\nThe demonstrated configuration has OPcache disabled, so the recorded filename belongs to the request heap. A filename retained in persistent OPcache memory does not produce the same dangling pointer. Exploitability depends on how the affected script was loaded and whether its filename is request-owned.\r\n\r\n### Affected versions\r\n\r\nThe affected field was introduced in PHP 8.3.0, when `session_start()` began recording the file and line where a session was started in order to report them in the notice about an already active session. PHP 8.2 and earlier do not contain the field and are not affected.\r\n\r\n### Mitigation\r\n\r\nUpgrade to the fixed release for your PHP branch when it becomes available. The fix clears the recorded session filename and line number during sessi\n\nAffected packages: php:ext-session\nPatched: ext-session 8.3.37, ext-session 8.4.28, ext-session 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7","published_at":"2026-11-19T14:06:00Z","updated_at":"2026-11-19T19:01:04Z","fetched_at":"2026-11-21T19:15:07.553365Z","severity":"critical","cvss_score":9.2,"epss":0.99999,"is_kev":true,"has_exploit":true,"kev_due_date":"2026-10-29","vendor":"php","product":"ext-session","vuln_id":"CVE-2026-129481","vuln_ids":["CVE-2026-109618","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-6WMF-4RV5-P3RP","GHSA-G3VH-838C-65V7","GHSA-W8HW-W9FX-J79W"],"tags":["repo-advisory","php","CWE-416","CWE-459","security","repo:php/php-src"],"cluster_id":450,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/626","html":"https://vulnwatch.ve1ve2.com/item/626"}},{"id":628,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-jm4m-qfqx-967m / CVE-2026-129291: PHP-FPM epoll use-after-free can lead to local privilege escalation","summary":"PHP-FPM epoll use-after-free can lead to local privilege escalation\n\n### Summary\r\n\r\nPHP-FPM can dispatch an epoll event that refers to a freed worker record when worker output capture is enabled. An attacker who can execute PHP code in an unprivileged FPM worker can exploit this use-after-free to execute commands with the privileges of the FPM master, which commonly runs as root.\r\n\r\n### Details\r\n\r\nWhen `catch_workers_output` is enabled, the FPM master monitors pipes connected to worker stdout and stderr. The epoll registrations store pointers to event structures embedded in the corresponding worker record.\r\n\r\nWhen a worker exits, `fpm_child_close()` attempts to drain its output pipes. If a helper process still holds a pipe's write end open, the read can return `EAGAIN` instead of reaching EOF. In this case, the master closes the pipe's read descriptor without first removing its event or invalidating the descriptor number stored in the worker record. Cleanup of that record is deferred for one second.\r\n\r\nAn attacker can stop a newly forked sibling after it drops to the pool user but before it closes inherited descriptors. The stopped sibling retains the original pipe readers and epoll descriptor, keeping the original watch alive after the master closes its own descriptors. The delayed cleanup can then use a descriptor number that has already been reused, removing the wrong watch or failing to remove the original one before freeing the worker record. A subsequent write to the old pipe makes epoll return a pointer into the freed record.\r\n\r\nThe master passes that pointer to `fpm_event_fire()`, which reads and calls the event callback. The demonstrated exploit uses the stale output callback to write through a freed logging buffer, corrupt the allocator's free list, and replace the callback with a function that executes a command. Root command execution was reproduced from a `www-data` worker against unmodified PHP 8.5.12 Docker images on Linux arm64 and x86-64. The exploit is dependent on memory layout and process timing. Curl and OPcache were used to obtain memory addresses for the demonstrated chain; they are not required to trigger the underlying epoll use-after-free.\r\n\r\nThe affected delayed-cleanup path was introduced in PHP 8.1.20 and 8.2.7. The fix unregisters each stdio event while its original descriptor is still valid, closes the descriptor, and sets the stored descriptor to `-1` so that delayed cleanup cannot act on it again.\r\n\r\n### Impact\r\n\r\nExploitation requires local code execution in an FPM worker, an affected pool with `catch_workers_output` enabled, the epoll event backend, and the ability to manipulate worker lifetimes and retain inherited pipe descriptors. A root FPM master permits escalation from the pool user to root. If the master runs as an unprivileged user, successful exploitation is limited to that user's privileges. In a container, this grants the master's container privileges and does not by itself establish a container escape.\r\n\r\nThe underlying descriptor-lifetime error can also close another\n\nAffected packages: php:sapi-fpm\nPatched: sapi-fpm None, sapi-fpm 8.2.36, sapi-fpm 8.3.37, sapi-fpm 8.4.28, sapi-fpm 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m","published_at":"2026-11-19T14:05:55Z","updated_at":"2026-11-19T19:00:11Z","fetched_at":"2026-11-21T19:15:07.553367Z","severity":"high","cvss_score":8.8,"epss":0.01033,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"sapi-fpm","vuln_id":"CVE-2026-129291","vuln_ids":["CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","GHSA-JM4M-QFQX-967M"],"tags":["repo-advisory","php","CWE-416","security","repo:php/php-src"],"cluster_id":454,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/628","html":"https://vulnwatch.ve1ve2.com/item/628"}},{"id":640,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-w8hw-w9fx-j79w / CVE-2026-109618: RCE via OOM corruption","summary":"RCE via OOM corruption\n\n## Summary\r\n\r\nPHP uses `longjmp()` for out-of-memory (OOM) errors to exit the current context and abort handling of the request. In some contexts, request memory is temporarily reachable before it is fully initialized. If any allocation fails at that point, PHP does not properly account for the early exit and leaves the request memory in an invalid state. The failed allocation does not need to be related to the invalid memory. The request shutdown procedure may then read or branch on it. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).\r\n\r\n## Vulnerability\r\n\r\n### OOM strategies\r\n\r\nSeveral multipart parsing problems can let a request reach OOM while remaining within its apparent PHP limits:\r\n\r\n- A multipart request without a usable declared content length may pass the initial `post_max_size` check and continue supplying decoded body data.\r\n- A multipart part can contain an unrestricted number of headers. Representing these headers inside PHP can use substantially more memory than their wire representation, allowing a request within `post_max_size` to exhaust the normal `memory_limit`.\r\n- Empty file controls do not count towards `max_file_uploads` but still create the normal file metadata arrays. Nested field names multiply the generated array work.\r\n\r\nOOM can also be reached in application-specific ways when attacker-controlled input causes a sufficiently large allocation or repeated memory use.\r\n\r\n### Susceptibility\r\n\r\nApache mod_php unconditionally invokes the request shutdown procedure, even when request startup has failed. During request startup, automatic body parsing can exhaust the configured memory limit and exit the request in a context where state is temporarily invalid. Shutdown then processes this invalid state. This happens entirely before any application-specific code begins execution.\r\n\r\nFPM exits the child when request startup fails. This prevents consumption of the invalid state and removes the child from the pool. After normal startup, OOM may still be reached in a context failing to account for an early exit, with the invalid state being processed during request shutdown. Source analysis therefore supports FPM as susceptible, though no complete FPM exploit has been demonstrated for this SAPI.\r\n\r\nSource analysis indicates that FrankenPHP, analogous to Apache mod_php, calls the request shutdown procedure unconditionally, making it likely susceptible to application-independent attacks. LSAPI models FPM, with application-specific exploits being likely but unvalidated.\r\n\r\n## Mitigation\r\n\r\nThe patch removes `longjmp()` for OOM, avoiding an early exit out of contexts that do not properly account for it. It is replaced with a delayed, graceful soft OOM triggered at the next VM safe point, and an immediate hard OOM using `_exit()` if memory consumption reaches a second, higher threshold. The shutdown procedure will no longer see invalid state, and PHP's normal ability to limit memory\n\nAffected packages: php:php-src\nPatched: php-src 8.2.35, php-src 8.3.36, php-src 8.4.27, php-src 8.5.12","url":"https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w","published_at":"2026-10-21T13:34:25Z","updated_at":"2026-11-03T22:10:29Z","fetched_at":"2026-11-21T19:15:07.553376Z","severity":"critical","cvss_score":9.2,"epss":0.99999,"is_kev":true,"has_exploit":true,"kev_due_date":"2026-10-29","vendor":"php","product":"php-src","vuln_id":"CVE-2026-109618","vuln_ids":["CVE-2026-109618","CVE-2026-109619","GHSA-6WMF-4RV5-P3RP","GHSA-W8HW-W9FX-J79W"],"tags":["repo-advisory","php","CWE-416","CWE-755","CWE-824","CWE-1325","CWE-1419","security","repo:php/php-src"],"cluster_id":108,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/640","html":"https://vulnwatch.ve1ve2.com/item/640"}},{"id":641,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-6wmf-4rv5-p3rp / CVE-2026-109619: RCE via stale global state","summary":"RCE via stale global state\n\n## Summary\r\n\r\nPHP contains various global state, such as error, session, object and extension state that is retained by a worker but points to memory owned by one request. That state must be reset before the request memory is released. Some input, configuration, session and error handling operations run before normal initialization of the next request. They inadvertently access stale state not reset by the previous request before initialization has a chance to replace it, causing a use after free. A strategically crafted heap layout can produce full remote code execution (RCE).\r\n\r\nState can survive for more than one reason. A fatal error, including one caused by memory exhaustion, can abandon an operation before it performs its matching reset. A warning or other nonfatal diagnostic can also repopulate error state after that state was already cleared during shutdown. The request heap is then freed while the worker global field still refers to it. A later operation that runs before normal request initialization can consume the stale value.\r\n\r\nSuccessful exploitation of this vulnerability requires both a producer and a consumer. The producer is a PHP operation that stores state owned by one request in a location PHP can access later in a subsequent request. The consumer is a subsequent PHP operation that reads, frees, branches or otherwise acts on the stale state previously stored by the producer.\r\n\r\nA concrete vulnerability would arise under the following conditions:\r\n\r\n1. A reachable PHP operation stores request-owned state in a globally accessible location, acting as the producer.\r\n2. The state is not reset, or another operation repopulates it after its normal reset.\r\n3. PHP releases the request memory while the persistent worker retains the referring global state.\r\n4. The same worker handles another request.\r\n5. A PHP operation reads, frees, branches or otherwise acts on the stale state before normal request initialization resets it, acting as the consumer.\r\n\r\nThe demonstrated producing and consuming operations occur in different HTTP requests handled by the same worker. The exact affected versions, configuration and mitigations depend on the internal state affected by the producing operation.\r\n\r\n## Vulnerability\r\n\r\n### Producers\r\n\r\nA producing operation becomes dangerous when its request-owned state remains published after the request heap is freed. A fatal error can cause this by abandoning the operation before it resets the state. Fatal interruptions include parse and compile failures, uncaught errors, failure of `require`, and `Maximum execution time exceeded`.\r\n\r\nOOM can provide the same interruption when an affected error, exception, object or extension state was already published.\r\n\r\nEven a nonfatal diagnostic from extension or server cleanup during a later shutdown stage can repopulate new request-owned error information to the global state.\r\n\r\n### Consumers\r\n\r\nThere are two confirmed consumers before normal initialization.\r\n\r\n#### INI d\n\nAffected packages: php:php-src\nPatched: php-src 8.2.35, php-src 8.3.36, php-src 8.4.27, php-src 8.5.12","url":"https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp","published_at":"2026-10-21T13:34:13Z","updated_at":"2026-10-21T13:34:13Z","fetched_at":"2026-11-21T19:15:07.553377Z","severity":"critical","cvss_score":9.2,"epss":0.99999,"is_kev":true,"has_exploit":true,"kev_due_date":"2026-10-29","vendor":"php","product":"php-src","vuln_id":"CVE-2026-109618","vuln_ids":["CVE-2026-109618","CVE-2026-109619","GHSA-6WMF-4RV5-P3RP","GHSA-W8HW-W9FX-J79W"],"tags":["repo-advisory","php","CWE-416","CWE-755","CWE-824","CWE-1325","CWE-1419","security","repo:php/php-src"],"cluster_id":109,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/641","html":"https://vulnwatch.ve1ve2.com/item/641"}},{"id":649,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-7875-c8px-7q5f / CVE-2026-93682: Out-of-bounds read in the HTTP stream wrapper when following a redirect with an empty Location header","summary":"Out-of-bounds read in the HTTP stream wrapper when following a redirect with an empty Location header\n\n### Summary\n\nWhen the HTTP stream wrapper follows a redirect and the response carries a `Location` header with an empty value, the redirect code reads one byte past the end of the heap buffer holding the location. The value of that out-of-bounds byte decides which redirect target is built, so a malicious server controls whether the client is sent to the host root or to the current directory.\n\n### Details\n\nSince the fix for GHSA-52jp-hrpf-2jff (CVE-2025-1861), `php_stream_http_response_headers_parse()` stores the `Location` value in a heap buffer of exactly `location_len + 1` bytes:\n\nhttps://github.com/php/php-src/blob/a66f30d78e10773048720b4b5f279136fdd0a433/ext/standard/http_fopen_wrapper.c#L295-L301\n\nFor an empty header value that is a single byte holding only the NUL terminator. The redirect handling in `php_stream_url_wrap_http_ex()` treats any location that does not start with `/` as a relative path and dereferences the second byte to decide whether to join it with the directory of the current request path:\n\nhttps://github.com/php/php-src/blob/a66f30d78e10773048720b4b5f279136fdd0a433/ext/standard/http_fopen_wrapper.c#L1055-L1063\n\n`*(header_info.location+1)` is one byte after the allocation.\n\nBefore CVE-2025-1861 was fixed, the location lived in a fixed-size `char location[HTTP_HEADER_BLOCK_SIZE]` stack buffer and the same read stayed in bounds. The bug therefore exists only in 8.1.32+, 8.2.28+, 8.3.18+, 8.4.5+ and all 8.5 releases.\n\nThe fix replaces `strlen(header_info.location)` with `header_info.location_len` and guards the second-byte read with the length, so an empty `Location` deterministically redirects to the host root. It was submitted and merged publicly, outside the security process, in https://github.com/php/php-src/pull/23467. A follow-up in https://github.com/php/php-src/pull/23521 corrected the guard from `location_len > 0` to `location_len > 1`, restoring the long-standing resolution of a single-character relative `Location`.\n\n### PoC\n\nA server answering `HTTP/1.1 302 Found\\r\\nLocation:\\r\\nContent-Length: 0\\r\\n\\r\\n` to this client:\n\n```php\n\n['follow_location' => 1]]);\nfile_get_contents(\"http://host/a/b\", false, $ctx);\n```\n\nThe next request goes to `/` when the stray byte happens to be NUL and to `/a//` otherwise. Under Valgrind with `USE_ZEND_ALLOC=0`:\n\n```\nInvalid read of size 1\nat php_stream_url_wrap_http_ex (http_fopen_wrapper.c:1044)\nby php_stream_url_wrap_http (http_fopen_wrapper.c:1186)\nby _php_stream_open_wrapper_ex (streams.c:2206)\nby zif_file_get_contents (file.c:426)\nAddress is 0 bytes after a block of size 1 alloc'd\nat malloc\nby _emalloc\nby php_stream_http_response_headers_parse (http_fopen_wrapper.c:268)\n```\n\nThe regression tests are `ext/standard/tests/http/http_empty_location_redirect.phpt` and `http_single_char_location_redirect.phpt`.\n\n### Impact\n\nAn attacker who controls a server that a PHP applic\n\nAffected packages: php:ext-standard\nPatched: ext-standard 8.2.34, ext-standard 8.3.35, ext-standard 8.4.26, ext-standard 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-7875-c8px-7q5f","published_at":"2026-09-24T10:07:25Z","updated_at":"2026-09-25T19:54:11Z","fetched_at":"2026-11-21T19:15:07.553383Z","severity":"critical","cvss_score":9.8,"epss":0.00856,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-standard","vuln_id":"CVE-2026-93682","vuln_ids":["CVE-2025-1217","CVE-2025-1218","CVE-2025-1219","CVE-2025-14181","CVE-2025-1734","CVE-2025-1736","CVE-2025-1861","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-52JP-HRPF-2JFF","GHSA-7875-C8PX-7Q5F"],"tags":["repo-advisory","php","CWE-125","security","repo:php/php-src"],"cluster_id":478,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/649","html":"https://vulnwatch.ve1ve2.com/item/649"}},{"id":644,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-88hq-2827-7pg6 / CVE-2026-92842: OOB read / info leak in convert.* stream filters when line-break-chars contains NUL","summary":"OOB read / info leak in convert.* stream filters when line-break-chars contains NUL\n\n### Summary\n\nThe `convert.base64-encode`, `convert.quoted-printable-encode` and `convert.quoted-printable-decode` stream filters accept a `line-break-chars` option whose length is tracked separately from the string itself. The filter constructors duplicate the value with `pestrdup()`, which stops at the first NUL byte, while keeping the original length. When the filter later emits a line break it copies the recorded length out of the truncated allocation, reading past its end and placing adjacent heap bytes into the filter output.\n\n### Details\n\n`php_conv_base64_encode_ctor()` duplicates the option with `pestrdup()` but stores the untruncated length:\n\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/standard/filters.c#L237-L238\n\n`php_conv_qprint_encode_ctor()` and `php_conv_qprint_decode_ctor()` repeat the same pattern at lines 838 and 1051. The over-read happens when the encoder inserts a line break and copies `lbchars_len` bytes from that allocation:\n\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/standard/filters.c#L406\n\nWith `line-break-chars` set to `\"\\0X\"` the duplicate is a one-byte allocation holding only the NUL terminator, while `lbchars_len` is still 2, so one byte past the allocation is copied into the output. Extending the option after the NUL increases the number of bytes read out of bounds.\n\nThe fix replaces `pestrdup()` with `pestrndup(lbchars, lbchars_len, persistent)` in all three constructors, so the allocation always matches the recorded length.\n\n### PoC\n\n```sh\nUSE_ZEND_ALLOC=0 ASAN_OPTIONS=detect_leaks=0 ./sapi/cli/php -n -r '\n$opts = [\"line-length\" => 4, \"line-break-chars\" => \"\\0X\"];\n$fp = fopen(\"php://temp\", \"r+\");\nfwrite($fp, str_repeat(\"A\", 6));\nrewind($fp);\nstream_filter_append($fp, \"convert.base64-encode\", STREAM_FILTER_READ, $opts);\necho bin2hex(stream_get_contents($fp)), \"\\n\";\n'\n```\n\nThe line break in the output should be the two bytes `0058`. Instead the second byte comes from adjacent memory, and AddressSanitizer reports:\n\n```\n==1271431==ERROR: AddressSanitizer: heap-buffer-overflow\nREAD of size 2 at 0x7bb9d15e2731 thread T0\n0x7bb9d15e2731 is located 0 bytes after 1-byte region [0x7bb9d15e2730,0x7bb9d15e2731)\n#1 php_conv_base64_encode_convert ext/standard/filters.c:406\n#2 strfilter_convert_append_bucket ext/standard/filters.c\n#3 strfilter_convert_filter ext/standard/filters.c:1513\n```\n\nThe same leak is reachable over HTTP wherever an application forwards request data into the filter options:\n\n```php\n\n4,\n\"line-break-chars\" => base64_decode($_GET[\"lb64\"]), // e.g. \"\\0X\"\n];\n$fp = fopen(\"php://temp\", \"r+\");\nfwrite($fp, str_repeat(\"A\", 6));\nrewind($fp);\nstream_filter_append($fp, \"convert.base64-encode\", STREAM_FILTER_READ, $opts);\necho bin2hex(stream_get_contents($fp));\n```\n\n### Impact\n\nHeap memory adjacent to the `line-break-chars` allocation is copied into the filter output, so an application that returns\n\nAffected packages: php:ext-standard\nPatched: ext-standard 8.2.34, ext-standard 8.3.35, ext-standard 8.4.26, ext-standard 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-88hq-2827-7pg6","published_at":"2026-09-24T10:07:21Z","updated_at":"2026-09-25T21:09:54Z","fetched_at":"2026-11-21T19:15:07.553379Z","severity":"medium","cvss_score":5.9,"epss":0.00277,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-standard","vuln_id":"CVE-2026-92842","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-88HQ-2827-7PG6"],"tags":["repo-advisory","php","CWE-122","CWE-125","security","repo:php/php-src"],"cluster_id":472,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/644","html":"https://vulnwatch.ve1ve2.com/item/644"}},{"id":12632,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-ch8v-r6jh-4vvr: ext/filter: encode 0xFF in FILTER_SANITIZE_ENCODED","summary":"ext/filter: encode 0xFF in FILTER_SANITIZE_ENCODED\n\n### Summary\n\n`php_filter_encode_url()` builds a 256-entry lookup table that decides which bytes `FILTER_SANITIZE_ENCODED` percent-encodes, but initialises only the first 255 entries. Entry 255 is read uninitialised, so whether the byte `0xFF` is encoded or passed through depends on whatever happened to be on the stack.\n\n### Details\n\nThe table is filled with `memset(tmp, 1, sizeof(tmp) - 1)`, which leaves `tmp[255]` untouched:\n\nhttps://github.com/php/php-src/blob/php-8.5.9/ext/filter/sanitizing_filters.c#L73\n\nThe filter then consults `tmp[*s]` for every input byte, so for `0xFF` the decision comes from uninitialised stack memory. Every other byte is handled deterministically.\n\nThe fix changes the `memset()` length to `sizeof(tmp)` so the whole table is initialised.\n\n### PoC\n\n```php\n<?php\n$out = filter_var(\"\\xff\\xfeabc\", FILTER_SANITIZE_ENCODED);\necho \"in : \", bin2hex(\"\\xff\\xfeabc\"), \"\\n\";\necho \"out: \", bin2hex($out), \"\\n\";\n```\n\n```\nin : fffe616263\nout: ff254645616263\n```\n\n`0xFE` is percent-encoded as `%FE` while `0xFF` is passed through raw, showing that `tmp[255]` was read uninitialised.\n\n### Impact\n\nThe impact is low. There is no crash and no memory corruption; the only effect is that the `0xFF` byte is sanitised inconsistently, depending on uninitialised stack contents. A downstream consumer that relies on `FILTER_SANITIZE_ENCODED` producing fully percent-encoded output could in principle be affected as part of a longer chain, but the filter provides no such guarantee on its own.\n\nThis issue was fixed publicly in 8.4.25 and 8.5.10 before it was recognised as security relevant, and is backported here to the branches that receive security fixes only.\n\n\nAffected packages: other:ext-filter\nPatched: ext-filter 8.2.34, ext-filter 8.3.35, ext-filter 8.4.25, ext-filter 8.5.10","url":"https://github.com/php/php-src/security/advisories/GHSA-ch8v-r6jh-4vvr","published_at":"2026-09-24T10:07:15Z","updated_at":"2026-09-24T10:07:15Z","fetched_at":"2026-11-22T14:05:37.431177Z","severity":"low","cvss_score":3.7,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-filter","vuln_id":"GHSA-ch8v-r6jh-4vvr","vuln_ids":["GHSA-CH8V-R6JH-4VVR"],"tags":["repo-advisory","other","security","repo:php/php-src","stack"],"cluster_id":11741,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12632","html":"https://vulnwatch.ve1ve2.com/item/12632"}},{"id":645,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-62xp-839h-2637 / CVE-2026-91768: IPv6 ACL bypass in FastCGI listen.allowed_clients due to partial address comparison (memcmp 12 bytes)","summary":"IPv6 ACL bypass in FastCGI listen.allowed_clients due to partial address comparison (memcmp 12 bytes)\n\n### Summary\r\n\r\nThe IPv6 branch of the FastCGI client access check compares only the first 12 bytes of a 16-byte IPv6 address, so `listen.allowed_clients` matches on a /96 prefix instead of the exact address. An attacker who can source an address sharing the first 96 bits with an allowed one passes the check and reaches the FastCGI endpoint.\r\n\r\n### Details\r\n\r\n`fcgi_is_allowed()` in `main/fastcgi.c` compares IPv6 client addresses with a hard-coded length of 12:\r\n\r\nhttps://github.com/php/php-src/blob/php-8.5.10/main/fastcgi.c#L1334\r\n\r\nAn exact IPv6 comparison must cover all 16 bytes of `struct in6_addr`. The IPv4 branch above it compares its full 4 bytes correctly, and the `IN6_IS_ADDR_V4MAPPED` branch legitimately uses a 12-byte offset to reach the embedded IPv4 address, but that offset is not a valid length for a plain IPv6 comparison. Allowed addresses are parsed as full addresses with `inet_pton(AF_INET6, ...)`, so the truncated comparison silently widens every configured entry to a /96 network.\r\n\r\nThe fix compares `sizeof(client_sa.sa_inet6.sin6_addr)` bytes.\r\n\r\n### PoC\r\n\r\nTested against a real `php-fpm` (fpm-fcgi), not a mock.\r\n\r\n1. Configure a pool:\r\n\r\n```ini\r\nlisten = [::1]:19091\r\nlisten.allowed_clients = ::2\r\n```\r\n\r\n2. Run php-fpm and send a FastCGI request from `::1` to `[::1]:19091` for a test script.\r\n\r\n3. The request is accepted and the script executes, even though `::1` is not in `listen.allowed_clients`. Both addresses share the first 96 bits.\r\n\r\n4. Control test: set `listen.allowed_clients = 2001:db8::2` and send the same request from `::1`. The connection is denied as expected, because the first 96 bits differ.\r\n\r\n### Impact\r\n\r\nThis is an access control bypass in deployments that use FastCGI over IPv6 TCP and rely on `listen.allowed_clients` as a security boundary. An attacker with network reachability who can source an address within the same /96 as an allowed client bypasses the ACL and reaches the FastCGI endpoint, which in many deployments means executing PHP scripts in the FPM worker context.\r\n\r\nDeployments using Unix sockets, IPv4 only, or an external firewall as the actual boundary are not affected.\r\n\r\n### Credit\r\n\r\nThis issue was originally reported in GHSA-r37j-mv37-rjpc. That advisory could not be used because the reporting account was deleted.\r\n\n\nAffected packages: php:PHP-FPM\nPatched: PHP-FPM 8.2.34, PHP-FPM 8.3.35, PHP-FPM 8.4.26, PHP-FPM 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-62xp-839h-2637","published_at":"2026-09-24T10:06:55Z","updated_at":"2026-09-25T21:04:06Z","fetched_at":"2026-11-21T19:15:07.553380Z","severity":"medium","cvss_score":6.5,"epss":0.00376,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"PHP-FPM","vuln_id":"CVE-2026-91768","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-62XP-839H-2637","GHSA-R37J-MV37-RJPC"],"tags":["repo-advisory","php","security","repo:php/php-src"],"cluster_id":473,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/645","html":"https://vulnwatch.ve1ve2.com/item/645"}},{"id":643,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-vvx9-73fr-5jjx / CVE-2026-91769: TLS Hostname Verification Falls Back to CN After SAN Mismatch","summary":"TLS Hostname Verification Falls Back to CN After SAN Mismatch\n\n### Summary\n\nPHP's OpenSSL stream peer verification checks the certificate's subjectAltName entries first and, whenever no entry matches, falls back to the Common Name. RFC 6125 requires the CN to be ignored once the certificate presents any service identity, so a certificate carrying a non-matching DNS SAN was still accepted when its CN matched the requested `peer_name`. A certificate trusted by the client for one name can therefore be used to impersonate another.\n\n### Details\n\n`php_openssl_apply_peer_verification_policy()` tries the SAN list and then unconditionally falls back to the CN:\n\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/openssl/xp_ssl.c#L635-L641\n\nIn the tested build a certificate with `CN=victim.test` and `SAN=DNS:attacker.test` was accepted for `peer_name=victim.test`. A control certificate with `CN=other.test` and the same SAN was rejected, confirming that acceptance came from the CN and that a SAN mismatch did not suppress the fallback.\n\nThe fix makes `php_openssl_matches_san_list()` report whether the certificate presented a service identity, meaning a DNS SAN, a URI SAN, or an SRV-ID `otherName` (OID 1.3.6.1.5.5.7.8.7). When one is present and none matched, verification now fails with `Peer certificate subjectAltName did not match expected name` instead of consulting the CN. Certificates with no service identity at all keep the CN fallback for backwards compatibility.\n\n### PoC\n\nCertificate for the accepted case:\n\n```ini\n[req]\ndistinguished_name = dn\nprompt = no\nx509_extensions = v3_req\n\n[dn]\nCN = victim.test\n\n[v3_req]\nsubjectAltName = @alt_names\nextendedKeyUsage = serverAuth\n\n[alt_names]\nDNS.1 = attacker.test\n```\n\nThe rejected control uses the same file with `CN = other.test`.\n\n```php\n\n[\n'verify_peer' => true,\n'verify_peer_name' => true,\n'allow_self_signed' => false,\n'cafile' => $argv[2],\n'peer_name' => $argv[3] ?? 'victim.test',\n],\n'http' => ['ignore_errors' => true, 'timeout' => 5],\n]);\n\n$data = @file_get_contents($argv[1], false, $ctx);\necho $data === false ? \"FAIL\\n\" : \"OK\\n\";\n```\n\nSteps:\n\n1. Create a local CA certificate.\n2. Issue one server certificate with `CN=victim.test` and `SAN=DNS:attacker.test`.\n3. Issue a control certificate with `CN=other.test` and the same SAN.\n4. Serve each certificate in turn from a local TLS server.\n5. Run the client with `peer_name=victim.test` and the CA certificate.\n\nThe first certificate prints `OK` (accepted) and the control prints `FAIL`.\n\n### Impact\n\nA certificate that a client trusts for one hostname can be used to impersonate a different hostname, as long as the attacker's certificate carries the target name in its Common Name. This matters where certificates come from a private PKI, an internal CA, or any environment where an attacker can obtain a certificate whose CN it does not control the SAN for. It affects eve\n\nAffected packages: php:ext-openssl\nPatched: ext-openssl 8.2.34, ext-openssl 8.3.35, ext-openssl 8.4.26, ext-openssl 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-vvx9-73fr-5jjx","published_at":"2026-09-24T10:06:51Z","updated_at":"2026-10-04T16:04:33Z","fetched_at":"2026-11-21T19:15:07.553378Z","severity":"medium","cvss_score":4.3,"epss":0.00159,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-openssl","vuln_id":"CVE-2026-91769","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-VVX9-73FR-5JJX"],"tags":["repo-advisory","php","security","repo:php/php-src"],"cluster_id":471,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/643","html":"https://vulnwatch.ve1ve2.com/item/643"}},{"id":646,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-xr7j-rvgx-xq5p / CVE-2026-91767: Heap-buffer-overflow in php_openssl_matches_wildcard_name on crafted server cert wildcard CN","summary":"Heap-buffer-overflow in php_openssl_matches_wildcard_name on crafted server cert wildcard CN\n\n### Summary\n\n`php_openssl_matches_wildcard_name()` in `ext/openssl/xp_ssl.c` underflows the length argument passed to `memchr()` when a TLS server certificate presents a wildcard name whose literal characters are together longer than the hostname being verified. A malicious server presenting such a certificate makes the PHP client read up to `SIZE_MAX` bytes past the end of a heap allocation. The path is reachable from any default client stream, because `verify_peer_name` is enabled by default.\n\n### Details\n\nThe guard before the `memchr()` call only accounts for the suffix length:\n\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/openssl/xp_ssl.c#L435-L441\n\nThe third argument is `subject_len - suffix_len - prefix_len`. `subject_len` and `suffix_len` are `size_t` while `prefix_len` is `ptrdiff_t`, so the usual arithmetic conversions promote the whole expression to `size_t`. With a certificate name of `aaa*aa` verified against `aaaa`, the prefix is 3 and the suffix is 2 against a 4-byte subject, so the length computes as `(size_t)(4 - 2 - 3)` and wraps to `SIZE_MAX`. `memchr()` then scans from `subjectname + prefix_len` until it finds a `.` or hits unmapped memory.\n\nThe fix makes `prefix_len` a `size_t` and changes the guard to `suffix_len + prefix_len <= subject_len`, so the subtraction can no longer wrap.\n\n### PoC\n\nCreate a CA and a server certificate whose CN is a wildcard pattern longer than the hostname:\n\n```sh\nmkdir -p /tmp/tls-poc && cd /tmp/tls-poc\nopenssl req -x509 -newkey rsa:2048 -keyout ca.key -out ca.crt -days 30 -nodes -subj \"/CN=poc-ca\"\nopenssl req -newkey rsa:2048 -keyout server.key -out server.csr -nodes -subj \"/CN=aaa*aa\"\nopenssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt -days 30\n```\n\nServe it from a local TLS listener, then run the client with a shorter `peer_name`:\n\n```php\n\n[\n'verify_peer' => true,\n'verify_peer_name' => true,\n'cafile' => '/tmp/tls-poc/ca.crt',\n'peer_name' => 'aaaa',\n],\n'http' => ['method' => 'GET', 'timeout' => 5],\n]);\n$body = @file_get_contents('https://127.0.0.1:18443/', false, $ctx);\nvar_dump(error_get_last());\n```\n\n```sh\nUSE_ZEND_ALLOC=0 ASAN_OPTIONS=detect_leaks=0:halt_on_error=0 ./sapi/cli/php repro.php\n```\n\n```\n==3801043==ERROR: AddressSanitizer: heap-buffer-overflow\nREAD of size 6559 at 0x50300003eac0 thread T0\n0x50300003eac0 is located 0 bytes after 32-byte region [0x50300003eaa0,0x50300003eac0)\n#1 php_openssl_matches_wildcard_name ext/openssl/xp_ssl.c:438\n#2 php_openssl_matches_common_name ext/openssl/xp_ssl.c:542\n#3 php_openssl_apply_peer_verification_policy ext/openssl/xp_ssl.c:635\n#4 php_openssl_enable_crypto ext/openssl/xp_ssl.c:1894\n```\n\n`USE_ZEND_ALLOC=0` is needed so that AddressSanitizer sees the boundary of the heap-allocated peer name; with the Zend allocator the read sti\n\nAffected packages: php:ext-openssl\nPatched: ext-openssl 8.2.34, ext-openssl 8.3.35, ext-openssl 8.4.26, ext-openssl 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-xr7j-rvgx-xq5p","published_at":"2026-09-24T10:06:47Z","updated_at":"2026-09-25T20:49:54Z","fetched_at":"2026-11-21T19:15:07.553381Z","severity":"medium","cvss_score":6.5,"epss":0.00107,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-openssl","vuln_id":"CVE-2026-91767","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-XR7J-RVGX-XQ5P"],"tags":["repo-advisory","php","CWE-122","security","repo:php/php-src"],"cluster_id":475,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/646","html":"https://vulnwatch.ve1ve2.com/item/646"}},{"id":652,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-r6x9-5r99-36j7 / CVE-2025-1218: Various packet overreads in mysqlnd_writeprotocol.c","summary":"Various packet overreads in mysqlnd_writeprotocol.c\n\n### Summary\r\n\r\nThe mysqlnd wire protocol parser reads fields out of server packets before checking that the packet still holds enough bytes for them. A malicious or compromised MySQL server can send a truncated packet and make the client read past the end of the packet buffer, which is undefined behaviour and can crash the process.\r\n\r\n### Details\r\n\r\n`BAIL_IF_NO_MORE_DATA` only guarantees that a single byte remains, but several call sites then read two or more bytes before re-checking. For example, the 2-byte read here happens before the over-read is detected:\r\n\r\nhttps://github.com/php/php-src/blob/8b682743196e765debb5056e56a97a67304f5e62/ext/mysqlnd/mysqlnd_wireprotocol.c#L871-L877\r\n\r\nThe same pattern occurs in the greeting, OK, EOF, auth-switch, cached-sha2, change-user, result-set header, prepared-statement response and row packet handlers. In addition, `php_mysqlnd_net_field_length()` and `php_mysqlnd_net_field_length_ll()` decode a length-encoded integer whose first byte selects a 3, 4 or 9 byte form, and read that many bytes without confirming they are present, so they can read 1 to 9 bytes out of bounds.\r\n\r\nThe fix replaces the single-byte guard with `BAIL_IF_NOT_ENOUGH_DATA_EX(n)`, which checks the exact number of bytes each read needs, and gives both field-length helpers a `remaining_size` argument so they return `MYSQLND_INVALID_NET_FIELD_LENGTH` instead of reading beyond the packet.\r\n\r\n### PoC\r\n\r\nThe regression tests added with the fix drive a fake MySQL server that emits truncated packets for each affected handler, for example `ext/mysqli/tests/ghsa-r6x9-5r99-36j7-greet-packet.phpt` and `ext/mysqli/tests/ghsa-r6x9-5r99-36j7-ok-packet-affected-rows.phpt`. Running them against an unpatched build under AddressSanitizer reports the out-of-bounds reads.\r\n\r\n### Impact\r\n\r\nApplications connecting to an untrusted or compromised MySQL server can be crashed, giving a denial of service. The bytes read past the buffer influence parsed field values but are not returned to the server, and the reads stay within the process heap. Applications that only connect to trusted database servers are not exposed.\r\n\n\nAffected packages: php:ext-mysqlnd\nPatched: ext-mysqlnd 8.2.34, ext-mysqlnd 8.3.35, ext-mysqlnd 8.4.26, ext-mysqlnd 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-r6x9-5r99-36j7","published_at":"2026-09-24T10:06:44Z","updated_at":"2026-09-25T18:15:30Z","fetched_at":"2026-11-21T19:15:07.553385Z","severity":"medium","cvss_score":5.9,"epss":0.00282,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-mysqlnd","vuln_id":"CVE-2025-1218","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-R6X9-5R99-36J7"],"tags":["repo-advisory","php","security","repo:php/php-src"],"cluster_id":483,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/652","html":"https://vulnwatch.ve1ve2.com/item/652"}},{"id":647,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-fpwc-w8rq-cr92 / CVE-2026-91766: Cross-origin credential leak in HTTP stream wrapper redirects","summary":"Cross-origin credential leak in HTTP stream wrapper redirects\n\n### Summary\n\nWhen the `http://` stream wrapper follows a redirect it forwards the user-supplied `Authorization`, `Cookie` and `Proxy-Authorization` headers unchanged, even when the redirect target is a different host, a different port, or a downgrade from HTTPS to HTTP. A server that can steer a redirect therefore receives credentials that were only meant for the original origin. This is the same class of issue that libcurl fixed in 7.58.0 (CVE-2018-1000007).\n\n### Details\n\nHeaders supplied through `stream_context_create()` are carried into the redirected request together with the rest of the context. Before the redirect is issued, the wrapper strips only `Content-Length` and `Content-Type`, and only when the method changes:\n\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/standard/http_fopen_wrapper.c#L703-L704\n\nThe flags handed to the recursive call carry no notion of the origin the credentials belong to:\n\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/standard/http_fopen_wrapper.c#L1133\n\nThe fix records the effective origin of the current request, being scheme, host and port with the default port filled in, and compares it with the parsed redirect target. When they differ, a new `HTTP_WRAPPER_STRIP_AUTH` flag is set and the three credential headers are removed from the user header bag before the next request is built. The flag is sticky, so credentials stay withheld for any further hops after a cross-origin one, matching libcurl's behaviour with `CURLOPT_UNRESTRICTED_AUTH` disabled.\n\nRemoving the last header from the bag also required `strip_header()` to drop the line break preceding it. Without that, the CRLF appended after the bag ends the header block early and the body of a body-preserving 307 or 308 redirect is corrupted. The same rewrite makes `strip_header()` scan line by line, so a repeated header, a folded continuation line, or the header name appearing inside another header's value can no longer leave the real header in place.\n\n### PoC\n\nA request to `https://example.com/api` carrying `Authorization: Bearer\n` that is answered with `302 Found` to `https://attacker.example/` results in the attacker's server receiving the `Authorization` header:\n\n```php\n\n[\n'header' => \"Authorization: Bearer SECRET\\r\\nCookie: sid=abc\",\n'follow_location' => 1,\n]]);\nfile_get_contents('https://example.com/api', false, $ctx);\n```\n\nThe regression test `ext/standard/tests/http/ghsa-fpwc-w8rq-cr92.phpt` runs two local servers on different ports and asserts that credentials are dropped on the cross-origin hop and on every hop after it, while being preserved when every hop stays on the same origin.\n\n### Impact\n\nAny application that uses `file_get_contents()`, `fopen()` or another `http://` stream with credential headers and leaves `follow_location` at its default is affected. An attacker who controls a redirect target, or a legitimate service that redirects to a th\n\nAffected packages: php:ext-standard\nPatched: ext-standard 8.2.34, ext-standard 8.3.35, ext-standard 8.4.26, ext-standard 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-fpwc-w8rq-cr92","published_at":"2026-09-24T10:06:39Z","updated_at":"2026-09-25T20:35:57Z","fetched_at":"2026-11-21T19:15:07.553381Z","severity":"medium","cvss_score":5.9,"epss":0.09906,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-standard","vuln_id":"CVE-2026-91766","vuln_ids":["CVE-2018-1000007","CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-FPWC-W8RQ-CR92","GHSA-G7X2-HRFP-PV5F"],"tags":["repo-advisory","php","CWE-200","CWE-522","security","repo:php/php-src"],"cluster_id":476,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/647","html":"https://vulnwatch.ve1ve2.com/item/647"}},{"id":12631,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-rgrp-mwpx-f6rm / CVE-2026-91765: SOAP: Unbounded Recursion in Server-Side cleanup_xml_node","summary":"SOAP: Unbounded Recursion in Server-Side cleanup_xml_node ### Summary `cleanup_xml_node()` in the SOAP XML parser recurses once per XML nesting level with no depth limit. An unauthenticated attacker can post a SOAP request containing tens of thousands of nested elements to any `SoapServer` endpoint, exhaust the stack and crash the process. The same unbounded recursion exists in the SOAP value decoder and in the WSDL node search helper. ### Details `cleanup_xml_node()` walks the parsed document to remove blank text and comment nodes and descends into every child without a depth counter: https://github.com/php/php-src/blob/php-8.5.10/ext/soap/php_xml.c#L39-L67 It runs after libxml2 has finished parsing, on the path taken by `SoapServer::handle()`: ``` SoapServer::handle() -> soap_xmlParseFile(\"php://input\") -> xmlCreateFileParserCtxt() -> xmlParseDocument() -> cleanup_xml_node(ctxt->myDoc->children) ``` libxml2 applies its own limits while parsing, but this traversal is PHP's own post-parse step and had none. `soap_xmlParseMemory()` has the call commented out, so the reachable path is the `php://input` one used by the server. Two further functions recurse on the same attacker-controlled structure: `master_to_zval_int()` in `ext/soap/php_encoding.c`, which follows `href` references and could also be driven into a cycle, and `get_node_with_attribute_recursive_ex()` in `ext/soap/php_xml.c`, which searches WSDL documents. The fix introduces `SOAP_MAX_XML_DEPTH` (2048) and `SOAP_MAX_DECODE_DEPTH`, rewrites `cleanup_xml_node()` and the WSDL search as iterative traversals, and tracks a decode depth in the SOAP globals so `href` chains and cycles are rejected rather than followed indefinitely. Documents nested deeper than the limit are refused before traversal. ### PoC ```php ' . str_repeat('', $depth) . str_repeat('', $depth) . ''; $ctx = stream_context_create(['http' => [ 'method' => 'POST', 'header' => \"Content-Type: text/xml\\r\\n\", 'content' => $body, ]]); file_get_contents('http://target/soap-endpoint.php', false, $ctx); ``` The target crashes with SIGSEGV inside `cleanup_xml_node()`. The payload is small on the wire, since 50,000 nested tags compress to a few kilobytes. No WSDL interaction, authentication or special configuration is required. The regression tests `ext/soap/tests/GHSA-rgrp-mwpx-f6rm.phpt`, `GHSA-rgrp-mwpx-f6rm-href-chain.phpt` and `GHSA-rgrp-mwpx-f6rm-href-cycle.phpt` cover the deep document, the `href` chain and the `href` cycle. ### Impact Any PHP application exposing a `SoapServer` endpoint can be crashed by a single unauthenticated HTTP request. Under PHP-FPM the worker handling the request dies, and a stream of such requests exhausts the worker pool and takes the endpoint offline. This is a denial of s Affected packages: php:ext-soap Patched: ext-soap 8.2.34, ext-soap 8.3.35, ext-soap 8.4.26, ext-soap 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-rgrp-mwpx-f6rm","published_at":"2026-09-24T10:06:35Z","updated_at":"2026-09-24T11:26:56Z","fetched_at":"2026-11-22T14:05:37.431174Z","severity":"high","cvss_score":7.5,"epss":0.00392,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2026-91765","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-RGRP-MWPX-F6RM"],"tags":["repo-advisory","php","security","repo:php/php-src","stack"],"cluster_id":462,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12631","html":"https://vulnwatch.ve1ve2.com/item/12631"}},{"id":648,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-cj93-vc83-wgqv / CVE-2025-14181: Integer overflow to buffer overflow in soap HTTP parsing","summary":"Integer overflow to buffer overflow in soap HTTP parsing\n\n### Summary\r\n\r\nThe SOAP HTTP client guards its response buffer growth with a check that relies on signed integer overflow, which is undefined behaviour and is not guaranteed to trigger. When the check is optimised away, a malicious SOAP server can make the client allocate a buffer far smaller than the data it then writes into it, producing a heap buffer overflow.\r\n\r\n### Details\r\n\r\n`get_http_body()` in `ext/soap/php_http.c` accumulates chunked response data and checks for overflow like this:\r\n\r\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/soap/php_http.c#L1494-L1499\r\n\r\n`http_buf_size` and `buf_size` are both `int`, so `http_buf_size + buf_size + 1 < 0` can only become true through signed integer overflow. That is undefined behaviour, and a compiler is free to assume it never happens and remove the branch. This was tested with Clang 20.1.7 and GCC 15.1.1, where the check did not trigger; other compilers and versions may behave differently, so the check cannot be relied upon.\r\n\r\nOnce the check is gone, `zend_string_realloc()` is reached with a length such as `18446744073709551614`. Adding the `zend_string` header overflows again, far too few bytes are allocated, and the following read loop writes past the end of the allocation.\r\n\r\nThe fix switches the accumulated size to `size_t`, bounds each growth step against `ZSTR_MAX_LEN` before allocating, and uses `zend_string_safe_realloc()` so the multiplication and addition are checked.\r\n\r\n### PoC\r\n\r\nA SOAP server that responds with `Transfer-Encoding: chunked` and declares a chunk size of `0x7fffffff`, followed by a second chunk header of the same size, drives the buffer size past `INT_MAX` on the reallocation for the second chunk. The regression test `ext/soap/tests/bugs/GHSA-cj93-vc83-wgqv.phpt` reproduces this against a local server. It needs several gigabytes of free memory, since the overflow is only reached after a genuinely large buffer has been built.\r\n\r\n### Impact\r\n\r\nA malicious SOAP server, or a man-in-the-middle on a plaintext SOAP connection, can overflow a heap buffer in a `SoapClient` that talks to it. The consequences depend on the heap layout and the compiler used to build PHP, ranging from a crash to memory corruption.\r\n\r\nThe bug only manifests on builds where the compiler discards the undefined signed-overflow check, and it requires the client to accept a multi-gigabyte response. Setting a low `memory_limit` causes an out-of-memory error before the overflow is reached and serves as a workaround.\r\n\n\nAffected packages: php:ext-soap\nPatched: ext-soap 8.2.34, ext-soap 8.3.35, ext-soap 8.4.26, ext-soap 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-cj93-vc83-wgqv","published_at":"2026-09-24T10:06:31Z","updated_at":"2026-09-25T20:22:43Z","fetched_at":"2026-11-21T19:15:07.553382Z","severity":"medium","cvss_score":6.5,"epss":0.00324,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2025-14181","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-CJ93-VC83-WGQV"],"tags":["repo-advisory","php","security","repo:php/php-src"],"cluster_id":477,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/648","html":"https://vulnwatch.ve1ve2.com/item/648"}},{"id":651,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-j3wh-g957-2m85 / CVE-2026-6103: Phar TAR phar_tar_number() Integer Overflow - Archive Entry Injection","summary":"Phar TAR phar_tar_number() Integer Overflow - Archive Entry Injection\n\n### Summary\r\n\r\n`phar_tar_number()` parses the octal size field of a TAR header into a `uint32_t` with no overflow check. The field is 11 octal digits wide and holds values up to `0x1FFFFFFFF`, so a size above `0xFFFFFFFF` silently wraps. The parser then skips the wrong number of data blocks and interprets attacker-controlled file content as the next TAR header, which lets a crafted archive inject entries that `PharData` reports and extracts as if they were genuine.\r\n\r\n### Details\r\n\r\nThe parser accumulates octal digits without bounding the result:\r\n\r\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/phar/tar.c#L23-L38\r\n\r\n| Octal field | True value | `uint32_t` result | Effect |\r\n|---|---|---|---|\r\n| `37777777777` | 0xFFFFFFFF | 4294967295 | largest value that does not wrap |\r\n| `40000000000` | 0x100000000 | 0 | size wraps to 0 |\r\n| `40000000001` | 0x100000001 | 1 | size wraps to 1 |\r\n| `40000001000` | 0x100000200 | 512 | size wraps to 512 |\r\n\r\nWhen the size wraps to 0 the parser reads the size at line 275, rounds it up to a block boundary at line 585 where `(0 + 511) & ~511` stays 0, then skips the data because the `size > 0` condition at line 587 is false. The next 512 bytes read are the entry's own data, parsed as a TAR header.\r\n\r\nThe GNU long filename path has an overflow check, but it only rejects `UINT_MAX` and `0`:\r\n\r\nhttps://github.com/php/php-src/blob/php-8.5.10/ext/phar/tar.c#L368\r\n\r\nA size that wraps to 1 passes it and allocates a one-byte buffer for what the header declares as a filename of more than 4 GB.\r\n\r\nGNU `tar` rejects the same archive with `not stopped at a record boundary`, while `PharData` accepts it and exposes the injected entries.\r\n\r\nThe fix replaces the size parse with `phar_tar_size()`, which accumulates into a `uint64_t`, rejects the GNU base-256 encoding, requires the whole field to be consumed, and refuses any value above `UINT32_MAX - 511`. It also introduces `phar_tar_type_has_data()` so the data blocks of every entry type that carries data are skipped, and rejects the unsupported GNU long link record outright.\r\n\r\n### PoC\r\n\r\n1. Build a TAR archive with a legitimate entry followed by an entry whose size field is `40000000000`.\r\n2. Place a valid TAR header in the data block immediately after that entry.\r\n3. Open the archive with `new PharData($file)`.\r\n\r\nThe injected header is parsed as a real entry with an attacker-chosen name, size and content, and appears in the manifest alongside the legitimate entries. Reading through `phar://` and extracting with `extractTo()` both return the injected version. Giving the injected entry the same name as a legitimate one replaces the original in the manifest, and a single overflow entry can introduce any number of further entries.\r\n\r\nThe regression tests `ext/phar/tests/tar/GHSA-j3wh-g957-2m85-size.phpt`, `-longlink.phpt` and `-typeflag.phpt` cover the wrapped size, the long filename check and the entry types that carry data.\r\n\r\n### Impact\r\n\r\nAn application that opens an untruste\n\nAffected packages: php:ext-phar\nPatched: ext-phar 8.2.34, ext-phar 8.3.35, ext-phar 8.4.26, ext-phar 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-j3wh-g957-2m85","published_at":"2026-09-24T10:06:27Z","updated_at":"2026-09-25T18:16:04Z","fetched_at":"2026-11-21T19:15:07.553384Z","severity":"medium","cvss_score":4.0,"epss":0.0021,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-phar","vuln_id":"CVE-2026-6103","vuln_ids":["CVE-2025-1218","CVE-2025-14181","CVE-2026-6103","CVE-2026-91765","CVE-2026-91766","CVE-2026-91767","CVE-2026-91768","CVE-2026-91769","CVE-2026-92842","CVE-2026-93682","GHSA-J3WH-G957-2M85"],"tags":["repo-advisory","php","security","repo:php/php-src"],"cluster_id":482,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/651","html":"https://vulnwatch.ve1ve2.com/item/651"}},{"id":650,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-9f67-6fw4-hpfp / CVE-2026-17545: PHP on Windows: Reserved Device Names Are Not Rejected Before File/Stream I/O which can cause DoS","summary":"PHP on Windows: Reserved Device Names Are Not Rejected Before File/Stream I/O which can cause DoS\n\n### Summary\r\n\r\nOn Windows, PHP's filesystem and stream APIs do not reject reserved device names such as `CON`, `PRN`, `AUX`, `NUL`, `COM1` to `COM9`, `LPT1` to `LPT9`, `CONIN$` and `CONOUT$` when they appear as a component of a path. An attacker-controlled filename therefore reaches `CreateFileW()` and opens a device instead of the regular file the application expected, which can block or hang the request and exhaust worker processes.\r\n\r\n### Details\r\n\r\nPaths from application code flow through the stream wrapper layer into the Windows I/O layer. `file_get_contents()` opens the requested path via `php_stream_open_wrapper_ex()`, and `move_uploaded_file()` reaches `VCWD_RENAME()` and `php_copy_file_ex()`, so paths built from user-controlled upload filenames arrive at the same place.\r\n\r\nThe Windows path validation macro checks only for trailing spaces and certain trailing dots:\r\n\r\nhttps://github.com/php/php-src/blob/php-8.5.10/win32/ioutil.h#L156-L169\r\n\r\nThere is no check for reserved device names, and `php_win32_ioutil_open_w()` passes the path straight to `CreateFileW()`:\r\n\r\nhttps://github.com/php/php-src/blob/php-8.5.10/win32/ioutil.c#L205\r\n\r\nThat device handles can result from ordinary file opening is visible further on, where a handle whose `GetFileType()` is `FILE_TYPE_CHAR` is marked as `S_IFCHR` in `win32/ioutil.c` and simply flagged as non-seekable in `main/streams/plain_wrapper.c`, rather than being rejected.\r\n\r\nThe fix adds `php_win32_ioutil_path_kind_w()` and `php_win32_ioutil_path_kind_a()`, which classify a path as ordinary, a bare device name, or a path containing a reserved component. Reserved components are rejected with `ERROR_INVALID_NAME` before any I/O, while bare device names such as `NUL` and `NUL:` keep working for backwards compatibility, and DOS device paths (`\\\\.\\`, `\\\\?\\` and `\\??\\`) are left alone because Windows does not map device names inside them. Variants such as `NUL.txt`, `aux:stream` and `NUL ` are resolved through `RtlIsDosDeviceName_U` so that PHP follows the behaviour of the Windows version it runs on.\r\n\r\n### PoC\r\n\r\n```php\r\n<?php\r\n$base = 'C:\\\\temp\\\\php-poc';\r\n$file = $_GET['file'] ?? 'test.txt';\r\n$path = $base . DIRECTORY_SEPARATOR . $file;\r\n\r\necho \"path = \" . $path . PHP_EOL;\r\necho file_get_contents($path);\r\n```\r\n\r\nRequesting the script with `?file=CON`, `?file=CONIN$` or `?file=NUL.txt` makes PHP open the corresponding device rather than failing on a missing file. `CONIN$` blocks waiting for console input, which holds the request open.\r\n\r\nThe regression test is `ext/standard/tests/file/ghsa-9f67-6fw4-hpfp-win32.phpt`.\r\n\r\n### Impact\r\n\r\nA PHP application on Windows that builds a path from user input, such as a download endpoint or an upload destination taken from the client-supplied filename, can be made to operate on a device instead of a file. Depending on the device and the operation this blocks or hangs the request, produces unexpected read and write behaviour, or returns errors from the native API. Under c\n\nAffected packages: other:php-src\nPatched: php-src 8.2.34, php-src 8.3.35, php-src 8.4.26, php-src 8.5.11","url":"https://github.com/php/php-src/security/advisories/GHSA-9f67-6fw4-hpfp","published_at":"2026-09-24T10:06:19Z","updated_at":"2026-09-25T18:16:20Z","fetched_at":"2026-11-21T19:15:07.553384Z","severity":"medium","cvss_score":6.9,"epss":0.00368,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-17545","vuln_ids":["CVE-2026-17545","GHSA-9F67-6FW4-HPFP"],"tags":["repo-advisory","other","CWE-67","security","repo:php/php-src"],"cluster_id":480,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/650","html":"https://vulnwatch.ve1ve2.com/item/650"}},{"id":642,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-vc5h-9ppw-p5f3 / CVE-2026-7260: Stack overflow in phar with circular symlinks","summary":"Stack overflow in phar with circular symlinks\n\n`phar_get_link_source()` in `ext/phar/util.c` recursively follows symbolic links in phar archives without any depth limit or cycle detection. A crafted tar-based phar archive containing circular symlinks causes unbounded recursion, exhausting the C stack and crashing the PHP process.\r\n\r\nhttps://github.com/php/php-src/blob/cbc0489126a7682796aad1e5fb4e51de74af162c/ext/phar/util.c#L60-L82\r\n\r\n```bash\r\npython3 -c \"\r\nimport tarfile\r\nwith tarfile.open('circular_symlinks.tar', 'w') as tar:\r\n    a = tarfile.TarInfo(name='file_a'); a.type = tarfile.SYMTYPE; a.linkname = 'file_b'; tar.addfile(a)\r\n    b = tarfile.TarInfo(name='file_b'); b.type = tarfile.SYMTYPE; b.linkname = 'file_a'; tar.addfile(b)\r\n\"\r\n\r\nphp -r '\r\n$p = new PharData(\"circular_symlinks.tar\");\r\n$p[\"file_a\"]->getContent();\r\n'\r\n# Expected: Segmentation fault (stack overflow)\r\n```\n\nAffected packages: php:ext-phar\nPatched: ext-phar 8.2.33, ext-phar 8.3.33, ext-phar 8.4.24, ext-phar 8.5.9","url":"https://github.com/php/php-src/security/advisories/GHSA-vc5h-9ppw-p5f3","published_at":"2026-07-30T11:03:15Z","updated_at":"2026-10-06T20:13:35Z","fetched_at":"2026-11-21T19:15:07.553378Z","severity":"medium","cvss_score":5.5,"epss":0.00114,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-phar","vuln_id":"CVE-2026-7260","vuln_ids":["CVE-2026-17543","CVE-2026-17544","CVE-2026-7260","GHSA-VC5H-9PPW-P5F3"],"tags":["repo-advisory","php","CWE-400","CWE-674","security","repo:php/php-src"],"cluster_id":470,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/642","html":"https://vulnwatch.ve1ve2.com/item/642"}},{"id":12633,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-x692-q9x7-8c3f / CVE-2026-17544: Out-of-bounds write in bccomp() via crafted operand and scale","summary":"Out-of-bounds write in bccomp() via crafted operand and scale\n\nA call to `bccomp()` with attacker-supplied inputs can lead to an out-of-bounds write to either stack or heap memory. The bug occurs in `bc_str2num()` when the scale truncates a number whose trailing zeros are subsequently trimmed.\r\n\r\nhttps://github.com/php/php-src/blob/a480965c90b4f4948f211c8b139788371e031838/ext/bcmath/libbcmath/src/str2num.c#L169-L185\r\n\r\n`str_scale` later determines the number of digits after the decimal point in the resulting string.\r\n\r\nhttps://github.com/php/php-src/blob/a480965c90b4f4948f211c8b139788371e031838/ext/bcmath/libbcmath/src/str2num.c#L203\r\n\r\nThe string is later populated using `bc_copy_and_toggle_bcd(nptr, fractional_ptr, fractional_end)`.\r\n\r\nhttps://github.com/php/php-src/blob/a480965c90b4f4948f211c8b139788371e031838/ext/bcmath/libbcmath/src/str2num.c#L213\r\n\r\nNote that we have shortened the allocated string (`str_scale -= fractional_end - fractional_new_end;`) but have not adjusted `fractional_end` itself. Consequently, `bc_copy_and_toggle_bcd(nptr, fractional_ptr, fractional_end)` will copy the original, untruncated string into a buffer that is too small, leading to an out-of-bounds write.\r\n\r\nBCMath uses a small stack-allocated arena for numbers before falling back to heap allocation, enabling both stack and heap corruption, depending on where the buffer is allocated.\r\n\r\nThe patch adds `fractional_end = fractional_new_end;` after the zero truncation.\r\n\n\nAffected packages: php:ext-bcmath\nPatched: ext-bcmath 8.4.24, ext-bcmath 8.5.9","url":"https://github.com/php/php-src/security/advisories/GHSA-x692-q9x7-8c3f","published_at":"2026-07-30T11:03:07Z","updated_at":"2026-07-30T11:03:07Z","fetched_at":"2026-11-22T14:05:37.431177Z","severity":"critical","cvss_score":9.8,"epss":0.00418,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-bcmath","vuln_id":"CVE-2026-17544","vuln_ids":["CVE-2026-17543","CVE-2026-17544","CVE-2026-7260","GHSA-X692-Q9X7-8C3F"],"tags":["repo-advisory","php","CWE-121","CWE-787","security","repo:php/php-src","stack"],"cluster_id":11742,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12633","html":"https://vulnwatch.ve1ve2.com/item/12633"}},{"id":12634,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-7qpv-r5mr-78m4 / CVE-2026-17543: SQL injection in ext-pgsql via E'...' backslash breakout","summary":"SQL injection in ext-pgsql via E'...' backslash breakout\n\n`php_pgsql_convert()` is used to convert and escape user-provided parameters in `pg_insert()`, `pg_update()`, `pg_select()`, and `pg_delete()`. It does so using `PQescapeStringConn()` and then wraps the result in an escape string constant, `E'...'` (via `php_pgsql_add_quotes()`).\r\n\r\nhttps://github.com/php/php-src/blob/cbc0489126a7682796aad1e5fb4e51de74af162c/ext/pgsql/pgsql.c#L4751-L4757\r\n\r\nWith `standard_conforming_strings = on` (the default since PostgreSQL 9.1), `PQescapeStringConn()` does not correctly escape values for the escape string constant `E'...'`, as it does not escape `\\` under this configuration. When `PQescapeStringConn()` escapes `'` as `''`, an attacker can trivially terminate the string by escaping the first single quote.\r\n\r\n```php\r\n$result = pg_select($db, 'user', ['name' => \"zzz\\\\' OR 1=1 --\"]);\r\n// SELECT * FROM \"user\" WHERE \"name\"='zzz\\'' OR 1=1 --';\r\nvar_dump($result); // returned all rows\r\n```\r\n\r\nNote that the doubled `\\\\` is a PHP escape sequence and that the `\\` appears only once in the parameter. Also note that `pg_select()` escapes the `'` by doubling it but does not escape the `\\`. Consequently, the first of the two `'` characters is escaped (meaning that it represents a literal `'`), while the second terminates the string. Everything after that is interpreted as part of the query.\r\n\r\nThe solution changes `php_pgsql_convert()` to wrap parameters in non-escaping string constants instead.\n\nAffected packages: php:ext-pgsql\nPatched: ext-pgsql 8.2.33, ext-pgsql 8.3.33, ext-pgsql 8.4.24, ext-pgsql 8.5.9","url":"https://github.com/php/php-src/security/advisories/GHSA-7qpv-r5mr-78m4","published_at":"2026-07-30T11:02:39Z","updated_at":"2026-07-30T11:02:39Z","fetched_at":"2026-11-22T14:05:37.431178Z","severity":"critical","cvss_score":9.8,"epss":0.0033,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-pgsql","vuln_id":"CVE-2026-17543","vuln_ids":["CVE-2026-17543","CVE-2026-17544","CVE-2026-7260","GHSA-7QPV-R5MR-78M4"],"tags":["repo-advisory","php","CWE-89","security","repo:php/php-src","stack"],"cluster_id":11743,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12634","html":"https://vulnwatch.ve1ve2.com/item/12634"}},{"id":12636,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-mhmq-mmqj-2v39 / CVE-2026-12184: Failure to setup TLS with a remote server can result in a remote DoS","summary":"Failure to setup TLS with a remote server can result in a remote DoS\n\n### Summary\r\n\r\nIn `php_stream_url_wrap_http_ex`, when TLS crypto setup fails (via `php_stream_xport_crypto_setup` or `php_stream_xport_crypto_enable`), the stream is closed and reset to `NULL`.\r\nHowever, the subsequent peer name cleanup block unconditionally tries to reset the peer name.\r\nThis is triggerable via a failure to validate the peer name or an expired certificate.\r\n\r\nAs demonstrated by https://github.com/php/php-src/issues/21468 this is triggerable without requiring specially-crafted code, and with a remote server.\r\n\r\n### Details\r\n\r\nPatch available via https://github.com/php/php-src/pull/21031\r\n\r\n### Impact\r\n\r\nThe impact is a remotely-triggerable DoS bringing the entire fpm process down with all its workers.\r\n\r\n### Additional Information\r\n\r\nThis was first discovered by a hybrid static-dynamic analyzer I'm developing.\nPatched:  8.3.32,  8.4.21,  8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-mhmq-mmqj-2v39","published_at":"2026-07-02T17:01:28Z","updated_at":"2026-07-02T17:01:28Z","fetched_at":"2026-11-22T14:05:37.431179Z","severity":"high","cvss_score":8.2,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-12184","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-MHMQ-MMQJ-2V39"],"tags":["repo-advisory","security","repo:php/php-src","stack"],"cluster_id":11745,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12636","html":"https://vulnwatch.ve1ve2.com/item/12636"}},{"id":12635,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-7jrw-539f-x6vr / CVE-2026-14355: ext/openssl: Memory corruption (zend_mm_heap corrupted) in openssl_encrypt with AES-WRAP-PAD","summary":"ext/openssl: Memory corruption (zend_mm_heap corrupted) in openssl_encrypt with AES-WRAP-PAD\n\n### Summary\r\nUsate of AES-WRAP-PAD can result in memory corruption and abort of application. \r\n\r\n### Details\r\n\r\nThe output buffer for the AES key-wrap-with-padding operation is sized from the plaintext length without accounting for RFC 5649 expansion. Key-wrap-with-pad rounds the plaintext up to the next 8-byte boundary and prepends an 8-byte AIV, so ciphertext length is roundup(len, 8) + 8, not a function of the raw input length. The zend_string PHP allocates is therefore too small for what OpenSSL's EVP_EncryptUpdate/EVP_EncryptFinal writes.\r\n\r\nOpenSSL writes the full wrapped output past the end of the undersized heap allocation, corrupting adjacent Zend MM heap metadata. This surfaces as the zend_mm_heap corrupted abort — the allocator detecting corrupted bookkeeping on a later operation, not at the moment of the overflow.\r\n\r\nFurther details in https://github.com/php/php-src/issues/22186 \r\n\r\n### Impact\r\n\r\nIf the attacker is able to find implementation using this rarely used algorithm, it can potentially abort the application and possibly cause DoS for the application.\nPatched:  8.2.32,  8.3.32,  8.4.23,  8.5.8","url":"https://github.com/php/php-src/security/advisories/GHSA-7jrw-539f-x6vr","published_at":"2026-07-02T16:56:26Z","updated_at":"2026-07-02T17:02:14Z","fetched_at":"2026-11-22T14:05:37.431178Z","severity":"medium","cvss_score":5.3,"epss":0.00279,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-14355","vuln_ids":["CVE-2026-14355","GHSA-7JRW-539F-X6VR"],"tags":["repo-advisory","security","repo:php/php-src","stack"],"cluster_id":11744,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12635","html":"https://vulnwatch.ve1ve2.com/item/12635"}},{"id":12639,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-hmxp-6pc4-f3vv / CVE-2026-7262: NULL pointer dereference in SOAP apache:Map decoder with missing <value>","summary":"NULL pointer dereference in SOAP apache:Map decoder with missing `to_zval_map()` in `ext/soap/php_encoding.c` decodes `apache:Map` nodes. The `` branch correctly guards against missing keys, but the `` branch rechecks `xmlKey` instead of `xmlValue`: https://github.com/php/php-src/blob/0d9ff00394d9447992bb66ccb1cef3edf70576bd/ext/soap/php_encoding.c#L2780-L2788 In addition, `master_to_zval_int()` accesses `data->properties` without a `NULL` check, where `data` corresponds to the missing `` node. This branch is reachable when `SOAP_GLOBAL(typemap)` is set, i.e. when the SOAP server has a typemap configured. By embedding an `apache:Map` node with a missing `` node into the request, the process will segfault with a `NULL` pointer dereference violation. Under the described circumstances, DoS becomes trivial with the following example: ```php $request = << foo XML; $server = new SoapServer(null, [ 'uri' => 'urn:test', 'typemap' => [['type_name' => 'anything']], ]); $server->addFunction('test'); function test($m) {} $server->handle($request); ``` Affected packages: php:ext-soap Patched: ext-soap 8.2.31, ext-soap 8.3.31, ext-soap 8.4.21, ext-soap 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-hmxp-6pc4-f3vv","published_at":"2026-05-07T12:57:55Z","updated_at":"2026-05-07T12:57:55Z","fetched_at":"2026-11-22T14:05:37.431181Z","severity":"high","cvss_score":7.5,"epss":0.0078,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2026-7262","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-HMXP-6PC4-F3VV"],"tags":["repo-advisory","php","security","repo:php/php-src","stack"],"cluster_id":11748,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12639","html":"https://vulnwatch.ve1ve2.com/item/12639"}},{"id":12640,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-m33r-qmcv-p97q / CVE-2026-7261: SoapServer session-persisted object use-after-free via SOAP header fault","summary":"SoapServer session-persisted object use-after-free via SOAP header fault `SOAP_PERSISTENCE_SESSION` allows to persist the SOAP handler object between requests using the session storage. Normally the object is immediately released after `SoapServer::handle()`, unless this setting is specified. This differentiation happens with the `service->soap_class.persistence != SOAP_PERSISTENCE_SESSION` check. `soap.c` fails to account for this flag in two places: https://github.com/php/php-src/blob/0d9ff00394d9447992bb66ccb1cef3edf70576bd/ext/soap/soap.c#L1595 https://github.com/php/php-src/blob/0d9ff00394d9447992bb66ccb1cef3edf70576bd/ext/soap/soap.c#L1600 Both of them are failure cases when a handler function for a header node either returned `false` or threw an exception. When the session is written, the freed object will be read and written to the session storage, resulting in a use-after-free. Normally, a SOAP server will only handle one SOAP request per PHP request, so it's unlikely that the attacker will be able to control the freed memory segment, though it is not impossible. The following example demonstrates the use-after-free. ```php class SoapSrv { public function return() { return new SoapFault('Server', 'denied'); } public function hello() { return 'ok'; } } session_start(); $srv = new SoapServer(null, ['uri' => 'urn:a']); $srv->setClass('SoapSrv'); $srv->setPersistence(SOAP_PERSISTENCE_SESSION); $srv->handle(<< XML); ``` Affected packages: php:ext-soap Patched: ext-soap 8.2.31, ext-soap 8.3.31, ext-soap 8.4.21, ext-soap 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q","published_at":"2026-05-07T12:57:35Z","updated_at":"2026-05-07T12:57:35Z","fetched_at":"2026-11-22T14:05:37.431181Z","severity":"critical","cvss_score":9.8,"epss":0.00302,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2026-7261","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-M33R-QMCV-P97Q"],"tags":["repo-advisory","php","security","repo:php/php-src","stack"],"cluster_id":11749,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12640","html":"https://vulnwatch.ve1ve2.com/item/12640"}},{"id":12641,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-wm6j-2649-pv75 / CVE-2026-7259: Null pointer dereference in php_mb_check_encoding() via mb_ereg_search_init()","summary":"Null pointer dereference in php_mb_check_encoding() via mb_ereg_search_init()\n\nThe following PHP code triggers a segmentation fault due to a NULL pointer dereference:\r\n\r\n```php\r\n<?php\r\nmb_regex_encoding('iso-8859-11');\r\n$test_str = 'x';\r\n\r\nif (mb_ereg_search_init($test_str)) {\r\n    $val = mb_ereg_search_pos(\"x\");\r\n    var_dump($val);\r\n} else {\r\n    var_dump(false);\r\n}\r\n```\r\n\r\nThe crash occurs due to a mismatch between Oniguruma and mbfl encoding support:\r\n\r\n1. **Oniguruma** (the regex library) supports `iso-8859-11` (Thai encoding)\r\n2. **mbfl** (mbstring's internal encoding library) does **NOT** support `iso-8859-11`\r\n\r\nhttps://github.com/php/php-src/blob/0d9ff00394d9447992bb66ccb1cef3edf70576bd/ext/mbstring/php_mbregex.c#L404-L413\r\n\r\nWhen `mb_regex_encoding('iso-8859-11')` is called:\r\n- `php_mb_regex_set_mbctype()` validates the encoding against Oniguruma → **succeeds**\r\n- `mbfl_name2encoding('iso-8859-11')` is called → returns **NULL**\r\n- `MBREX(current_mbctype_mbfl_encoding)` is set to **NULL**\r\n\r\nLater, when `mb_ereg_search_init()` calls `php_mb_check_encoding()`:\r\n- `php_mb_regex_get_mbctype_encoding()` returns NULL\r\n- `php_mb_check_encoding()` dereferences the `NULL` pointer → **SEGV**\r\n\r\nThis vulnerability allows a denial of service (DoS). An attacker can reliably crash a PHP process when user-controlled input influences the encoding passed to `mb_regex_encoding()` and the application subsequently uses mbregex search APIs.\r\n\r\nEnumeration of all Oniguruma-supported encodings vs mbfl support:\r\n\r\n| Encoding / aliases | Oniguruma | mbfl | Status |\r\n|--------------------|-----------|------|--------|\r\n| iso-8859-1 … iso-8859-10 | ✓ | ✓ | Safe |\r\n| iso-8859-11, ISO8859-11 | ✓ | ✗ | **CRASH** |\r\n| iso-8859-13 … iso-8859-16 | ✓ | ✓ | Safe |\r\n| EUC-JP aliases: UJIS | ✓ | ✗ | **CRASH** |\r\n| EUC-CN aliases: GB-2312 | ✓ | ✗ | **CRASH** |\r\n| KOI8 aliases: KOI-8R | ✓ | ✗ | **CRASH** |\r\n| ASCII aliases: US_ASCII, ISO646 | ✓ | ✗ | **CRASH** |\r\n| KOI8 (no suffix) | ✓ | ✗ | Safe (rejected by mb_regex_encoding()) |\r\n| All other encodings | ✓ | ✓ | Safe |\r\n\r\n### Credits\r\nViet Hoang Luu - The University of Melbourne\r\nAmirmohammad Pasdar - The University of Melbourne\r\nWachiraphan Charoenwet - The University of Melbourne\r\nShaanan Cohney - The University of Melbourne\r\nToby Murray - The University of Melbourne\r\nVan-Thuan Pham - The University of Melbourne\r\n\n\nAffected packages: php:ext-mbstring\nPatched: ext-mbstring 8.5.6, ext-mbstring 8.4.21, ext-mbstring 8.3.31, ext-mbstring 8.2.31","url":"https://github.com/php/php-src/security/advisories/GHSA-wm6j-2649-pv75","published_at":"2026-05-07T12:57:13Z","updated_at":"2026-05-07T12:57:13Z","fetched_at":"2026-11-22T14:05:37.431182Z","severity":"medium","cvss_score":6.5,"epss":0.00186,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-mbstring","vuln_id":"CVE-2026-7259","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-WM6J-2649-PV75"],"tags":["repo-advisory","php","CWE-476","security","repo:php/php-src","stack"],"cluster_id":11750,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12641","html":"https://vulnwatch.ve1ve2.com/item/12641"}},{"id":12642,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-7qg2-v9fj-4mwv / CVE-2026-6735: XSS within PHP-FPM status endpoint","summary":"XSS within PHP-FPM status endpoint Improper sanitization of the request URI within the PHP-FPM status page allows an attacker to execute arbitrary JavaScript code (XSS) on the victims machine, possibly stealing cookies on insufficiently hardened systems, or stealing other sensitive data such as the information from the status page itself. An attacker does not require authentication or access to the `/status` endpoint in order to trigger XSS, but may simply visit a URI embedding the malicious code. 1. Navigate to `example.com/` 2. Navigate to `example.com/status?full&html` 3. Observe the JavaScript pop-up. The same is possible for the XML endpoint, possibly embedding malicious XML nodes into the status report. 1. Navigate to `example.com/<` 2. Navigate to `example.com/status?full&xml` 3. Observe the XML parsing error. Affected packages: php:PHP-FPM Patched: PHP-FPM 8.2.31, PHP-FPM 8.3.31, PHP-FPM 8.4.21, PHP-FPM 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-7qg2-v9fj-4mwv","published_at":"2026-05-07T12:56:51Z","updated_at":"2026-05-07T12:56:51Z","fetched_at":"2026-11-22T14:05:37.431183Z","severity":"high","cvss_score":7.6,"epss":0.00193,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"PHP-FPM","vuln_id":"CVE-2026-6735","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-7QG2-V9FJ-4MWV"],"tags":["repo-advisory","php","CWE-79","security","repo:php/php-src","stack"],"cluster_id":465,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12642","html":"https://vulnwatch.ve1ve2.com/item/12642"}},{"id":12643,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-85c2-q967-79q5 / CVE-2026-6722: Use-After-Free in SOAP using Apache map with Remote Code Execution","summary":"Use-After-Free in SOAP using Apache map with Remote Code Execution ext-soap supports deduplicating objects in the XML graph through `id` and `href`. When traversing the XML graph, ext-soap will remember all plain PHP objects using the hash map `SOAP_GLOBAL(ref_map)`, where the pointer to the libxml2 node acts as a key, and the PHP object as a value. This happens in `soap_add_xml_ref()`. https://github.com/php/php-src/blob/dcf653339c245e25ea319248d0fc071a9405d688/ext/soap/php_encoding.c#L349-L354 Crucially, the reference count of the PHP object is _not_ increased. Normally this is not a problem, as all objects in the XML graph are stored in the resulting object graph and cannot be freed. `soap_check_xml_ref()` does the opposite of `soap_add_xml_ref()`; it will check whether some libxml2 node as already been evaluated and stored in `SOAP_GLOBAL(ref_map)`. https://github.com/php/php-src/blob/dcf653339c245e25ea319248d0fc071a9405d688/ext/soap/php_encoding.c#L331-L347 The Apache map offers a mechanism to free objects between these two points by overwriting existing map entries. ```php class Handler { public function test($map, $stale) { global $result; $result = $stale; } } $envelope = <<<'XML' somekey Stale somekey XML; $s = new SoapServer(null, ['uri' => 'urn:a']); $s->setClass(Handler::class); $s->handle($envelope); var_dump($result); ``` This example will: - evaluate the `map` node - evaluate the `Stale` object, which includes calling calling `soap_add_xml_ref()` to remember it in `SOAP_GLOBAL(ref_map)` - add the resulting object to a temporary map, which will be the result of the Apache map node - overwrite the object immediately with `NULL` for the `` with an empty ``, releasing the `Stale` object only strongly referenced by the temporary map, with the reference in `SOAP_GLOBAL(ref_map)` becoming stale - have `` refer to this stale pointer within `SOAP_GLOBAL(ref_map)`, reusing the freed memory After this code, `$result` will refer to the stale memory where `Stale` was previously allocated. The attacker has high control over this memory segment by subsequently allocating plain strings, leading to Remote Code Execution. The solution is straight forward, namely increase the reference c Affected packages: php:ext-soap Patched: ext-soap 8.2.31, ext-soap 8.3.31, ext-soap 8.4.21, ext-soap 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5","published_at":"2026-05-07T12:56:25Z","updated_at":"2026-05-07T12:56:25Z","fetched_at":"2026-11-22T14:05:37.431183Z","severity":"critical","cvss_score":9.8,"epss":0.00894,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-soap","vuln_id":"CVE-2026-6722","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-85C2-Q967-79Q5"],"tags":["repo-advisory","php","CWE-416","security","repo:php/php-src","stack"],"cluster_id":11751,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12643","html":"https://vulnwatch.ve1ve2.com/item/12643"}},{"id":12644,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-m8rr-4c36-8gq4 / CVE-2026-7258: Out-of-bounds read in urldecode()","summary":"Out-of-bounds read in urldecode() Consider the following snippet within `php_url_decode_ex()` at `ext/standard/url.c`, called from PHPs `urldecode()` function: https://github.com/php/php-src/blob/dcf653339c245e25ea319248d0fc071a9405d688/ext/standard/url.c#L592-L593 According to the C11 specification, `isxdigit()`'s (and all other `ctype.h` functions') only argument is of type `int`, and any value passed to it must be representable by `unsigned char`, i.e. 0-255. §7.4: > The header declares several functions useful for classifying and mapping characters. In all cases the argument is an int, the value of which shall be representable as an unsigned char or shall equal the value of the macro EOF. If the argument has any other value, the behavior is undefined. On platforms where plain `char` is signed (which is most), passing a `char` with a value <0 to `int` (or casting to `int` explicitly as in this case) will lead to signed integer extension, leading to a negative `int` value. Instead, the `char` value should be cast to `unsigned char`, so that no sign extension occurs. Most platforms account for this common mistake. However, on NetBSD passing negative values to `isxdigit()` lead to an out-of-bounds read, leading to a segfault. ```php urldecode(\"%\\x80\"); ``` Affected packages: php:php-src Patched: php-src 8.2.31, php-src 8.3.31, php-src 8.4.21, php-src 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-m8rr-4c36-8gq4","published_at":"2026-05-07T12:56:13Z","updated_at":"2026-05-07T12:56:13Z","fetched_at":"2026-11-22T14:05:37.431184Z","severity":"high","cvss_score":7.5,"epss":0.00363,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-7258","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-M8RR-4C36-8GQ4"],"tags":["repo-advisory","php","CWE-125","security","repo:php/php-src","stack"],"cluster_id":11752,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12644","html":"https://vulnwatch.ve1ve2.com/item/12644"}},{"id":12645,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-74r9-qxhc-fx53 / CVE-2026-6104: Global buffer over-read in mb_convert_encoding() with attacker-supplied encoding","summary":"Global buffer over-read in mb_convert_encoding() with attacker-supplied encoding ## Summary A global buffer over-read exists in `mbfl_name2encoding_ex()` (`ext/mbstring/libmbfl/mbfl/mbfl_encoding.c`, line 352), called from `mb_convert_encoding(...)` and other mbstring functions, when parsing encoding names with embedded NUL bytes. ## Root Cause In `mbfl_name2encoding_ex`, the MIME name search loop (line 352) uses: ```c if (strncasecmp((*encoding)->mime_name, name, name_len) == 0 && (*encoding)->mime_name[name_len] == '\\0') { ``` When `name` contains an embedded NUL byte (e.g., `\"UTF-8\\x00AAAA...\"`), `strncasecmp` returns 0 after matching up to the NUL (since both strings have NUL at the same position). The subsequent check `(*encoding)->mime_name[name_len]` then reads at offset `name_len` (e.g., 22) from `mime_name`, which is only 6 bytes long (`\"UTF-8\\0\"`). This reads 16+ bytes past the end of the global string into adjacent global memory. The same issue exists on lines 362 for encoding aliases. ## Minimal Reproducer ```php","url":"https://github.com/php/php-src/security/advisories/GHSA-74r9-qxhc-fx53","published_at":"2026-05-07T12:55:25Z","updated_at":"2026-05-07T12:55:25Z","fetched_at":"2026-11-22T14:05:37.431185Z","severity":"critical","cvss_score":9.1,"epss":0.00469,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-mbstring","vuln_id":"CVE-2026-6104","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-74R9-QXHC-FX53"],"tags":["repo-advisory","php","CWE-125","security","repo:php/php-src","stack"],"cluster_id":11753,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12645","html":"https://vulnwatch.ve1ve2.com/item/12645"}},{"id":12646,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-w476-322c-wpvm / CVE-2025-14179: SQL injection in pdo_firebird via NUL bytes in quoted strings","summary":"SQL injection in pdo_firebird via NUL bytes in quoted strings\n\nImproper handling of NUL bytes during the preparation of Firebird SQL queries leads to sections of the of the query being dropped. NUL bytes can find their way into queries even under regular circumstances via `PDO::quote()`.\r\n\r\nhttps://github.com/php/php-src/blob/046ffa257581d6f1a709e9fbc4638793c2ac7e22/ext/pdo_firebird/firebird_driver.c#L437-L442\r\n\r\nA new query is constructed token-by-token. In the case of a `ttString` `'\\0'`, the string is copied via `strncat()` rather than `memcpy()`, stopping after the first `'` quote and ignoring both the `\\0` and terminating `'` quote. This will incorrectly embed the SQL tokens following the string into the string, allowing for trivial SQL injection if the next string is also attacker-controlled.\r\n\r\n```php\r\n$dbh->exec('CREATE TABLE users (name VARCHAR(255))');\r\n$dbh->exec(\"INSERT INTO users VALUES ('Foo')\");\r\n$dbh->exec(\"INSERT INTO users VALUES ('Bar')\");\r\n\r\n$param = $dbh->quote(\"\\0\");\r\n$param2 = $dbh->quote('or 1=1--');\r\n\r\n$stmt = $dbh->query(\"SELECT * FROM users WHERE name = {$param} AND name = {$param2}\");\r\n\r\n// Before preparation:\r\n// SELECT * FROM users WHERE name = '\\0' AND name = 'or 1=1--'\r\n\r\n// After preparation:\r\n// SELECT * FROM users WHERE name = ' AND name = 'or 1=1--'\r\n\r\necho json_encode($stmt->fetchAll(PDO::FETCH_ASSOC)) . \"\\n\";\r\n// [{\"NAME\":\"Foo\"},{\"NAME\":\"Bar\"}]\r\n```\r\n\r\nThis incorrect preparation applies to `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `WITH` and `EXECUTE` statements.\r\n\r\n## Credits\r\nAleksey Solovev, Nikita Sveshnikov (Positive Technologies)\n\nAffected packages: php:ext-pdo_firebird\nPatched: ext-pdo_firebird 8.2.31, ext-pdo_firebird 8.3.31, ext-pdo_firebird 8.4.21, ext-pdo_firebird 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-w476-322c-wpvm","published_at":"2026-05-07T12:55:05Z","updated_at":"2026-05-07T12:55:06Z","fetched_at":"2026-11-22T14:05:37.431185Z","severity":"critical","cvss_score":9.8,"epss":0.00439,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-pdo_firebird","vuln_id":"CVE-2025-14179","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-W476-322C-WPVM"],"tags":["repo-advisory","php","CWE-89","security","repo:php/php-src","stack"],"cluster_id":11754,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12646","html":"https://vulnwatch.ve1ve2.com/item/12646"}},{"id":12647,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-96wq-48vp-hh57 / CVE-2026-7568: Signed integer overflow in metaphone()","summary":"Signed integer overflow in metaphone() **Researcher: Aleksey Solovev (Positive Technologies)** The PHP standard library provides the function `metaphone()` (php-src/ext/standard/metaphone.c). This function is used for searching and matching words based on their phonetic sound. This function declares the variable `signed int w_idx`, keeping track of the current position into the string passed to `metaphone()`. https://github.com/php/php-src/blob/9498bc3ee131616344370f59d4f1a6bb46375750/ext/standard/metaphone.c#L171 The maximum value the `signed int` type can hold is (usually) `2_147_483_647`. In C, exceeding this value for signed types is undefined behavior. Frequently, the value will wrap around and result in the value `-2_147_483_648`, but this behavior is not guaranteed. If the string passed to `metaphone()` has a length of `>2_147_483_647`, a signed integer overflow can occur, resulting in undefined behavior. Accessing the current word after an overflow can result in a segmentation fault or access unrelated memory. ```php ``` ``` $ ./php cli.php AddressSanitizer:DEADLYSIGNAL ================================================================= ==2977930==ERROR: AddressSanitizer: SEGV on unknown address 0x74748ba00018 (pc 0x6051a40f8a68 bp 0x7ffca9b12420 sp 0x7ffca9b123d0 T0) ==2977930==The signal is caused by a READ memory access. #0 0x6051a40f8a68 in metaphone /home/administrator/php/php-src/ext/standard/metaphone.c:192 #1 0x6051a40f8433 in zif_metaphone /home/administrator/php/php-src/ext/standard/metaphone.c:43 #2 0x6051a4552725 in ZEND_DO_ICALL_SPEC_RETVAL_UNUSED_HANDLER /home/administrator/php/php-src/Zend/zend_vm_execute.h:1355 #3 0x6051a46b7f4a in execute_ex /home/administrator/php/php-src/Zend/zend_vm_execute.h:116436 #4 0x6051a46cd123 in zend_execute /home/administrator/php/php-src/Zend/zend_vm_execute.h:121924 #5 0x6051a4831146 in zend_execute_script /home/administrator/php/php-src/Zend/zend.c:1981 #6 0x6051a42653ef in php_execute_script_ex /home/administrator/php/php-src/main/main.c:2645 #7 0x6051a42657ff in php_execute_script /home/administrator/php/php-src/main/main.c:2685 #8 0x6051a4836cb6 in do_cli /home/administrator/php/php-src/sapi/cli/php_cli.c:951 #9 0x6051a4839283 in main /home/administrator/php/php-src/sapi/cli/php_cli.c:1362 #10 0x74758f42a1c9 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 #11 0x74758f42a28a in __libc_start_main_impl ../csu/libc-start.c:360 #12 0x6051a3406d04 in _start (/home/administrator/php/php-src/sapi/cli/php+0x606d04) (BuildId: 675b273c6c01d12f08faaf607fb51c198e4db43b) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/administrator/php/php-src/ext/standard/metaphone.c:192 in metaphone ==2977930==ABORTING ``` Affected packages: php:ext-standard Patched: ext-standard 8.2.31, ext-standard 8.3.31, ext-standard 8.4.21, ext-standard 8.5.6","url":"https://github.com/php/php-src/security/advisories/GHSA-96wq-48vp-hh57","published_at":"2026-05-07T12:54:56Z","updated_at":"2026-05-07T12:54:56Z","fetched_at":"2026-11-22T14:05:37.431186Z","severity":"high","cvss_score":7.5,"epss":0.00455,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-standard","vuln_id":"CVE-2026-7568","vuln_ids":["CVE-2025-14179","CVE-2026-12184","CVE-2026-6104","CVE-2026-6722","CVE-2026-6735","CVE-2026-7258","CVE-2026-7259","CVE-2026-7261","CVE-2026-7262","CVE-2026-7263","CVE-2026-7568","GHSA-96WQ-48VP-HH57"],"tags":["repo-advisory","php","CWE-125","CWE-190","security","repo:php/php-src","stack"],"cluster_id":11755,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12647","html":"https://vulnwatch.ve1ve2.com/item/12647"}}],"total":88,"has_more":true,"next_cursor":"MjAyNi0wNS0wN1QxMjo1NDo1Ni4wMDAwMDB8MTI2NDc","limit":50,"page":1,"grouped":false,"filter":{"builds":"exclude","source":"gh-php-src"}}