CVE-2026-129496 Magento is the identifier to search for a critical flaw in PHP itself, published on 2026-11-19. It affects Magento stores running PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 or 8.5 before 8.5.13, in specific non-thread-safe configurations. Because it can be triggered by an unauthenticated remote request, plan the PHP update soon.
- Severity: CVSS 4.0 score 9.2 CRITICAL (
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N). NVD status: Awaiting Analysis. - Affected versions: PHP before 8.2.36, 8.3. before 8.3.37, 8.4. before 8.4.28, 8.5.* before 8.5.13.
- Fixed in: PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
- What to do: update PHP to a fixed version (packages, hosting panel or container image) and restart PHP-FPM or Apache.
This is a flaw in the PHP runtime, not in Magento code. The fix is therefore a PHP update, not a Magento patch.
What the vulnerability is
The official description calls it a timezone cache use-after-free. The weaknesses listed are CWE-416 (use after free) and CWE-459 (incomplete cleanup).
In plain words, it works like this:
- PHP keeps a cache of timezone information.
- In non-thread-safe builds, a diagnostic can be written to a file-based
error_logwhile PHP modules are starting up. Examples given are an invaliddate.timezonevalue or a session configuration warning. - In that case the timezone cache is allocated in startup memory that is freed later, while PHP still keeps a reference to it.
- A diagnostic raised early in the first request of a worker, such as the
max_input_varswarning, then reads that freed memory.
Accessing memory after it has been released is a classic memory-safety bug. The outcome depends on what happens to occupy that memory.
AC:H, AT:P). Not every PHP installation below the fixed versions is exposed in practice, but you should not rely on that without checking. What an attacker can do
Per the official description, an unauthenticated remote attacker can crash PHP-FPM, Apache mod_php or CGI workers with a crafted request. No login to your store or admin is needed.
The description also states that arbitrary code execution may be possible and has been demonstrated with known memory addresses.
For a Magento shop, the possible consequences are:
- Downtime: repeated worker crashes can make the storefront and checkout slow or unavailable.
- Code running as the web user: this kind of flaw can let an attacker read configuration files, including database credentials and the encryption key in
app/etc/env.php. - Data exposure and tampering: customer data, orders and admin accounts become reachable if code execution succeeds. Skimming code could also be planted on the checkout.
The last two points describe what code execution generally allows. The official information does not report a specific incident against stores.
VC:H/VI:H/VA:H). If your PHP matches the conditions above, treat this as urgent despite the high attack complexity. Are you affected?
Check three things: the PHP version, the build type, and the error log setup.
1. The version serving the store
The command-line PHP can differ from the PHP-FPM or Apache module serving your shop. Check both:
php -vshows the CLI version.php-fpm -v(the binary name may carry a version suffix, such asphp-fpm8.3) shows the FPM version.- For Apache, check the PHP module package that is loaded.
php -v. The CLI result says nothing about the PHP that actually answers web requests, so always check the FPM or Apache module version too. If the version is below 8.2.36, 8.3.37, 8.4.28 or 8.5.13 for your branch, it is in the affected range. Versions below 8.2 are also covered by the "before 8.2.36" wording, and they no longer get fixes from the 8.2 line.
2. Thread safety
The flaw concerns non-thread-safe builds. Run php -i | grep -i "thread safety". A value of disabled means a non-thread-safe build, which is typical for PHP-FPM setups.
disabled result means you are in the build type the flaw concerns, so continue with the error log check and plan the update. 3. Error log and startup warnings
The trigger needs a diagnostic written to a file-based error_log during startup. Check the error_log setting in your php.ini and pool configuration. Also check whether your PHP logs show startup warnings, for example about date.timezone.
The official information does not say that this check proves you are safe. The simplest course is to update regardless.
Signs of compromise
The official information lists no indicators of compromise. Repeated crashed or unexpectedly restarted PHP workers, such as segmentation faults in system or PHP-FPM logs, are consistent with the crash behaviour described. They are not a confirmed signature. If you see them, update first and then review the server for unexpected files and changes.
How to fix it
1. Back up
Take a full backup of the database and the code, and a snapshot of the server if you can. Save your current PHP configuration files as well.
2. Test on staging
Install the fixed PHP version on a staging copy. Choose the fixed release of your current branch: 8.2.36, 8.3.37, 8.4.28 or 8.5.13. Check the official Magento system requirements before changing branch. Test checkout, admin login, indexing and cron.
3. Update PHP
Update the component that runs PHP:
- Own server: update the PHP packages from your distribution or PHP repository, including the FPM or Apache module package.
- Hosting panel: select the fixed PHP version, or ask your host to confirm the fix.
- Containers: rebuild the image on a fixed PHP base image and redeploy.
4. Restart the service
Restart PHP-FPM (or Apache if you use mod_php) so the running workers use the new binary. Until you restart, old workers keep running the vulnerable code.
5. Return to production
Repeat the update on production, ideally in a quiet period. Then watch the error logs for a while.
setup:upgrade or setup:di:compile. Flushing the cache with bin/magento cache:flush after the restart is a harmless precaution. If you cannot update today
The official information gives no workaround. What follows is general risk reduction, not a fix:
- Review startup warnings: the trigger described needs a diagnostic during startup. Correcting configuration errors such as an invalid
date.timezonevalue is good practice. The official information does not confirm it removes the risk. - Put a web application firewall or rate limiting in front of the store to reduce repeated crafted requests.
- Monitor PHP-FPM or Apache logs for crashing workers and set up alerts.
- Keep your admin hardening (IP restrictions, two-factor authentication). Note that this flaw needs no authentication, so those measures do not protect against it.
How to check the fix worked
- Run
php -vandphp-fpm -vand confirm 8.2.36, 8.3.37, 8.4.28, 8.5.13 or later on your branch. - Confirm the running processes were restarted after the update, for example by checking the PHP-FPM service start time.
- Check that a page served by the web server reports the new version, using a temporary diagnostic that you remove straight afterwards. The CLI version alone is not proof.
- Watch the logs for crashing workers over the next days.
- If your package keeps the old version number, confirm the fix in the package changelog or with your host.
FAQ
Is CVE-2026-129496 a Magento vulnerability?
No. It is in PHP, which Magento runs on. Any Magento store on an affected PHP build is exposed, so the fix is a PHP update.
Does the attacker need an account on my store?
No. The official description says an unauthenticated remote attacker can trigger it with a crafted request. The attack still requires specific conditions, reflected in the high attack complexity.
Is there a patch for Magento?
Not needed, and none is mentioned in the official information. Update PHP to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 or later. See the official advisory at https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv.
Has the score been confirmed by NVD?
The entry is marked Awaiting Analysis, so NVD has not finished its own assessment. The CVSS 4.0 score of 9.2 CRITICAL is the one listed with the entry.
Let us apply it for you
If you would rather not touch the server yourself, we can do it. We fix, build and migrate Magento 2 stores on an hourly basis, and you only pay for the time you use.
- Book the hours: estimate how many you need, or follow our suggested number through a direct link.
- We agree the details: you talk directly with the person doing the work, not an account manager, to settle what happens and when.
- We do the work: you receive a short report of what was done.
Our estimate for applying this fix on a typical store is 3 to 6 hours. That covers the backup, the staging test, the PHP update, the service restart and the final checks. Heavy customisations or a jump to a different PHP branch can take more.
Every booked hour you don't use stays available to you, with no imposed expiry, so booking the upper end of the range costs nothing extra if we finish sooner.


