Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →PHP's default session handler updates session files in place without clearing them first. Interrupt one write at the wrong moment and yesterday's session tail becomes today's unserialize input. That is CVE-2026-126714, the lead flaw in PHP's November 19, 2026 security release — and the fix is a version bump on every supported branch.
PHP's files session save handler — the default, the one most PHP apps run — writes updated session data into the existing session file without first clearing it. If a write is interrupted, the file can contain the beginning of the new session followed by the end of the old one, and bytes of an ordinary string can later be unserialized as objects. An attacker who can influence the session data — the record's example is session upload progress — and interrupt a write at a suitable point may inject objects, which can lead to code execution when the application contains a suitable gadget chain. Session data can also be corrupted outright.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H. Note the AT:P: attack requirements are present, and the preconditions below are part of the score, not footnotes to it.Any PHP app on the affected ranges using the default files session handler — which is most of them. Check php -v on the server or your host panel: you want 8.2.36, 8.3.37, 8.4.28, or 8.5.13 (or later) on your branch. Our free mini-scan now classifies the PHP version your site discloses publicly against this release's fixed table and flags an affected one — with all four preconditions stated, because that is the honest claim the version alone supports. A site that discloses no version is reported as unverified, never as vulnerable.
In-place update of a serialized store is a corruption primitive. Clear-then-write — or write-temp-then-rename — is the only safe shape, and "the write is fast, it won't be interrupted" is not a control. The same shape shows up anywhere a process rewrites a file it later trusts: caches, queues, lockfiles. If your code rewrites a trusted file in place, the interrupt window is the vulnerability, whether or not anyone has found it yet.
Related: php2shell: Two Critical PHP RCEs Were Patched Today — the October release that fixed the same branches one patch earlier.
Running PHP? Run the free check at preshipit.com/free-scan — it reads the PHP version your site announces and flags the November release range, preconditions and all.
The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report