CVE-2026-129182: PHP patch for potential remote code execution
This text was generated using artificial intelligence (AI).On November 19, 2026, CVE-2026-129182 was released for the PHP engine. The vulnerability affects PHP versions from 8.5.0 to before 8.5.13. PHP 8.5.13 contains the fix.
The vulnerability has a CVSS-4.0 score of 9.2. Under certain configuration conditions, it can cause memory corruption and crashes of PHP workers. Remote code execution is possible. An active exploitation of CVE-2026-129182 is not known at the time of release.
CVE-2026-129182 is a use-after-free error. During the request shutdown, modified INI settings can be restored. If this process leads to a fatal error, the stored backtrace of a fatal error can be filled again after the executor has already been cleaned up.
The request memory is then released. If the same PHP-FPM or mod_php worker provides a diagnosis during a later request before the executor initialization, it can access the no longer valid backtrace. This can lead to memory corruption and worker crashes; remote code execution is possible under the described conditions.
The vulnerability affects deployments with PHP-FPM or mod_php. A path-specific configuration of max_memory_limit is required for the error during shutdown. The combination of zlib.output_compression and output_handler can also be relevant; these settings can be overridden by .user.ini .
For later diagnosis, directory-specific configurations are relevant in Apache. In PHP-FPM, the PHP_VALUE– or PHP_ADMIN_VALUE-parameters of the front-end system can play a role.
Patch and interim measure
The intended resolution is the upgrade to PHP 8.5.13.
If an immediate upgrade is not possible, it can fatal_error_backtraces=0 be set administratively. All workers must then be restarted. Additionally, it must be ensured that request-specific configurations do not reactivate this setting.
Organizations with NIS-2 obligations in Germany and Austria, as well as organizations that fall under the revised Information Security Act (ISG) in Switzerland with reporting obligations to BACS, should check whether the vulnerability affects reportable systems. If a worker crash leads to a data protection incident concerning personal data, the reporting obligation under GDPR Art. 33 applies with a 72-hour deadline to the relevant supervisory authority. PHP-FPM is widely used in many German and Austrian web infrastructures; affected systems should be prioritized for patching.
Affected systems should be prioritized and mitigated. Continuous monitoring of vulnerabilities and risks among technology providers supports the further assessment of technical dependencies.
Visibility of publicly accessible PHP endpoints
For the assessment of CVE-2026-129182, it is initially relevant which publicly accessible web endpoints use PHP and whether PHP versions in the affected area become visible there. After that, the technical examination of the respective PHP-FPM, mod_php, and configuration paths is required.
LocateRisk EASM can make publicly accessible web endpoints and deployed software visible. This allows PHP endpoints to be identified where a check for affected versions and configuration conditions is necessary. The platform does not replace a technical verification of the actually deployed version or the configuration relevant to this vulnerability.
Cyber Vendor Risk Management (C-VRM) complements this view of one's own infrastructure by providing alerts when critical vulnerabilities become known among vendors or when their security level changes.
Am I affected?
The affected component is the PHP engine in the versions mentioned above; the vulnerability has been fixed in 8.5.13. Those who want to know whether the PHP engine is even visible in their externally accessible infrastructure can use the CVE Quick Check Use the tool at the end of this article: It shows exposed systems and the software that is visible from the outside.
It is not always possible to determine the specific version that has been installed from the outside—the key factor is comparing it with the manufacturer's advisory.
As a temporary measure, it can fatal_error_backtraces=0 be set administratively. After that, all workers must be restarted. It must also be ensured that request-specific configurations do not reactivate this setting. This measure does not replace a full upgrade.
Status: November 19, 2026. This contribution serves general informational purposes and is not legal, security, or action advice for individual cases. The security situation and patch availability may have changed since publication; the relevant linked manufacturer advisory is always decisive. Despite careful research, we assume no liability for the currentness, correctness, and completeness.
CVE Quick Check
In just a few minutes, check whether there are any indications of a current CVE on your externally visible attack surface.
Initial assessment in just a few minutes via email.
Learn more during a free consultation with a LocateRisk consultant.
You'll receive this by email
companyYour Company, LLC
Verified CVECVE-2026-129182
Passive Assessment
Information About the CVEfound or not found
Want to find out more, book a demo or simply exchange ideas? We look forward to hearing from you!
We use cookies to optimize our website and our service.
Functional
Always active
Technical storage or access is strictly necessary for the lawful purpose of enabling the use of a particular service expressly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a message over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that have not been requested by the subscriber or user.
Statistics
The technical storage or access, which is carried out exclusively for statistical purposes.Technical storage or access used solely for anonymous statistical purposes. Without a subpoena, the voluntary consent of your Internet service provider, or additional records from third parties, information stored or accessed for this purpose alone generally cannot be used to identify you.
Marketing
Technical storage or access is necessary to create user profiles, to send advertisements, or to track the user on a website or across multiple websites for similar marketing purposes.