CVE-2026-14355 php vulnerability
In PHP versions 8.2.* before 8.2.32, 8.3.* before 8.3.32, 8.4.* before 8.4.23, 8.5.* before 8.5.8, the AES-WRAP-PAD algorithm implementation in OpenSSL extension contains a buffer allocation flaw. The output buffer for the AES key-wrap-with-padding operation is sized from the plaintext length without accounting for RFC 5649 expansion. This may cause OpenSSL to write beyond allocated memory, corrupting heap metadata and triggering application abort.
Quick answer
php should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 8.2.0 through before 8.2.32
- 8.3.0 through before 8.3.32
- 8.4.0 through before 8.4.23
- 8.5.0 through before 8.5.8
Fixed versions
- 8.2.32
- 8.3.32
- 8.4.23
- 8.5.8
How to fix it
CVE-2026-14355 affects the PHP OpenSSL extension. It may corrupt memory and crash an app. Update each PHP branch to 8.2.32, 8.3.32, 8.4.23, 8.5.8, or move to a newer supported PHP release.
- List every server, container, and job that runs PHP.
- Check the PHP branch and exact version on each system.
- Upgrade PHP to one of the fixed versions: 8.2.32, 8.3.32, 8.4.23, 8.5.8.
- Rebuild containers and redeploy apps that bundle PHP.
- Restart PHP-FPM, web servers, workers, and cron jobs after patching.
- Review logs for crashes in OpenSSL encryption code.
- Patch Debian or other OS packages if PHP comes from the OS vendor.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Run php -v and confirm the version is 8.2.32, 8.3.32, 8.4.23, 8.5.8 or newer for its branch.
- Confirm deployed containers use the rebuilt PHP image.
- Run the app test suite for encryption and login flows.
- Check logs again and confirm the crash pattern stopped.
- Record the patched package version and deploy time.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-14355?
php versions listed as affected should be reviewed: 8.2.0 through before 8.2.32, 8.3.0 through before 8.3.32, 8.4.0 through before 8.4.23, 8.5.0 through before 8.5.8.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.