What is phpAfterShell?
phpAfterShell is the name researchers gave CVE-2026-126714, a critical vulnerability in PHP’s file-based session handler. PHP sessions help applications remember information between requests, such as a signed-in user’s state. The PHP maintainers’ advisory rates the issue 9.2 out of 10 under CVSS v4.0.
An interrupted session update can leave a mixture of old and new data in a session file. Under specific conditions, a later request may interpret that data as objects, potentially leading to code execution with the PHP worker’s permissions. Authentication requirements depend on how the application exposes session operations. The researchers describe a demonstrated chain in their technical writeup.
This is a separate vulnerability from October’s PHP2Shell issues. Installing the October fixes alone does not install the November phpAfterShell fix.
Which applications need attention?
The defect affects PHP’s files session handler, its default. A vulnerable runtime using file-based sessions is in scope; whether code execution is possible depends on the application, configuration, and other conditions. Session stores such as Redis or a database are outside this specific file-write defect, though they still need their own security review.
Custom PHP applications, websites, and platforms may use sessions differently. Check production, staging, development, containers, and every server handling requests. The PHP version shown at the command line can differ from the one serving the website.
PHP 8.1 and older are no longer supported by the PHP project. Ask your vendor about supported backports or plan a move to a supported branch; do not assume all older packages share the same mitigation status.
Install the November PHP security update.
On November 19, PHP released the versions below. The first four are the fixed branch releases identified in the maintainers’ advisory; PHP 8.6.0 was also released with the fix. Review the PHP changelog and your vendor’s guidance for the complete security release.
| PHP branch | Fixed release |
|---|---|
| 8.2 | 8.2.36 |
| 8.3 | 8.3.37 |
| 8.4 | 8.4.28 |
| 8.5 | 8.5.13 |
| 8.6 | 8.6.0 |
Distribution vendors may backport fixes without changing the upstream version number. Verify the full installed package revision against the vendor’s advisory. Apply the update across serving nodes and restart the relevant PHP services and workers so the updated runtime is actually loaded.
If you cannot update immediately.
Ask your administrator to review the official advisory. Disabling session upload progress when it is not needed can remove one input path, but it does not eliminate every way an application can place untrusted data in sessions. A suitable alternative session store may avoid this specific file-write defect; the PHP update remains the recommended fix. Test configuration changes and application functionality.
Request a clear patch confirmation.
Send this to your hosting provider or the person responsible for your infrastructure. Do not wait for a sales call to apply an available security update.
Please confirm whether our PHP environments have been reviewed for CVE-2026-126714 and the November 19 PHP security releases. Which PHP runtime and package revision serve each application? Are sessions stored in files? Have the relevant packages been updated and PHP services and workers restarted? Please identify any outstanding work or temporary mitigations.
- Identify the owner and inventory. Include production, staging, containers, and older systems.
- Check the runtime and session storage. Confirm the web-serving PHP version and vendor package revision, not only the command-line version.
- Apply the vendor updates. Coordinate compatibility, backups, and any required operating system upgrades. Restart affected services and workers.
- Verify critical workflows. Test login, sessions, forms, uploads, and scheduled work after the update. Record what was completed and what remains.
- Investigate concerns. Preserve relevant logs and escalate signs of compromise. An update does not establish whether earlier exposure was exploited.
Infrastructure. Security review. Ongoing care.
Security updates are easier to manage when responsibility for infrastructure and the application is clear. Our services provide a starting point for that conversation.
Managed Hosting Infrastructure Plans
Choose dedicated, single-tenant infrastructure with defined monitoring and nightly app-server snapshots. Higher tiers add separation and redundancy for the application your team uses every day.
Hosting fees cover the agreed infrastructure. Setup, routine maintenance and technical oversight, security assessments, recovery work, and other labor are scoped separately. Offsite backups and extended retention are also separate. We agree on who handles PHP and OS updates and the associated labor before work begins.
Explore Managed Hosting Infrastructure Plans →Managed Security Assessments
Give your developers a prioritized view of issues found in an agreed codebase. Our assessments combine AI-assisted analysis with human review at the level included in your selected package. Reviewed Assessment adds focused validation of significant findings; Assessment + Retest adds an agreed follow-up check.
Source-code access is required. These assessments review application code; they do not certify that a PHP runtime is patched, include live-site penetration testing, or replace incident investigation. Code fixes are scoped separately.
Explore Managed Security Assessments →Systems Care
For applications already built by 417 Solutions, Systems Care provides agreed routine maintenance, technical oversight, monitoring and backups within the agreed setup, and an hours bank for small improvements. Coverage and priority response windows are defined in the agreement.
Infrastructure fees are separate. Major features and larger changes require a change order or new phase. We define how maintenance work, including runtime or operating system upgrades, fits your agreement.
Explore the Systems Care package →Start with the system you have.
Book a free strategy call to discuss your application and its support needs. New builds and larger changes follow paid Discovery, a formal proposal, and a build. Scope and pricing are agreed before work begins.
Answers for your next decision.
We patched PHP2Shell. Do we need another update?
Yes. The October upstream releases addressed the original PHP2Shell vulnerabilities; phpAfterShell is a separate flaw. Verify the November update or your vendor’s equivalent backport.
Does disabling upload progress solve the issue?
It can reduce exposure through one path, but applications may put untrusted data into sessions in other ways. Follow the PHP advisory and update the runtime.
Will a security assessment patch our PHP server?
Our Managed Security Assessments review agreed application source code. They require source access and do not certify the server’s patch status. Server updates and code fixes are separately scoped.
Read the original guidance.
Reviewed November 19, 2026. Check these sources for later updates and vendor-specific instructions.