PHP Security Updates for November 2026
The PHP project has announced another set of security patches. Our Seiden PHP+ Server has been updated with these fixes; this article will review the fixes that matter to our users. While last month’s security issues were remotely exploitable in a default PHP installation, this round of vulnerabilities (and most in general) often require specific configurations or scenarios that aren’t likely to occur in all applications . That said, you should update regardless. We recommend Seiden Support for all users of PHP in a critical IBM i environment so that we can keep you updated and help you patch and answer all your questions.
CGI: GHSA-5j3f-64r7-f564
Seiden PHP+ by default uses php-cgi in FastCGI mode, so this fix pertains to us, but the exploit requires complex rewrite rules, where a shorter path (like /news/my-post) is rewritten into a longer one passed to the PHP script (like /content/articles/my-post). Several other conditions are needed for the exploit to occur, though. The exploit relies a PHP bug where it uses the longer latter path to calculate lengths on the shorter path, allowing out-of-bounds memory access that could be used for further exploitation. Seiden Support clients can feel free to ask us if the exploit applies to them.
If you don’t use rewrite rules, or only pass in paths verbatim to a script (this is likely if you are using rewrites), then this is not immediately relevant. If you are, and cannot update immediately, you can turn on cgi.fix_pathinfo=0 , but verify your application’s router still works.
PHAR: GHSA-68fq-fh7h-f8gr
PHAR allows for PHP programs like Composer to be distributed as a single file. With this vulnerability, an attacker can change a signed PHAR archive through an algorithm downgrade, allowing them to change the contents even if you verify the signature.
If you download and use .phar binaries, it’s recommended you put the public key for them beside it as <archive filename>.pubkey. For our Composer package that uses PHAR, the RPM itself is signed and the permissions only allow a security officer to replace the file.
HTTPS: GHSA-f6gg-rchx-xw8j
If you’re using PHP’s own streams functionality to do HTTP/FTP requests (not curl, but i.e file_get_contents), then an upper-case S in the protocol name (such as httpS or HTTPS) would treat the connection as plaintext instead of secure.
If you can’t update, make sure all URLs are properly cased in your application.
HTTP client: GHSA-mmf9-xm3v-hg2x
If you’re using PHP’s own streams functionality to do HTTP/FTP requests (not curl, but i.e file_get_contents), a malicious server on the other end can manipulate the HTTP headers it sends in a way to make PHP waste CPU time processing the request.
This requires a malicious server on the other end, and can only perform a denial of service; no attacker control or information leakage is possible.
SOAP: GHSA-q23r-hr55-xmpg
A malicious SOAP payload (for both the server or client) that has an empty/whitespace-only arraySize will make an empty array, but PHP will still attempt to read the first element. This can allow for leaking contents of uninitialized memory that can help an attacker chained with other exploits, but by itself can’t crash or corrupt memory.
If you cannot update, you can validate that the contents of a SOAP message don’t contain an invalid arraySize.
Seiden is here to support you
Contact us to discuss a Seiden PHP+ Server support arrangement or upgrading to Seiden PHP+ Server to get to a supported PHP release level and answer all your questions.

Leave a Reply
Want to join the discussion?Feel free to contribute!