Edition of Saturday 21 November 2026

PhpAfterShell: From Interrupted Session Writes to Remote Code Execution

Comments on “PhpAfterShell: From Interrupted Session Writes to Remote Code Execution”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

depthfirst disclosed phpAfterShell (CVE-2026-126714, CVSS 4.0 score 9.2), a PHP flaw that bypasses the earlier php2shell fix. During multipart upload-progress updates, PHP rewrites the file-backed session in place with non-atomic pwrite() and ftruncate(). If the worker dies mid-update, the file can hold a valid but spliced session that later session_start() deserializes. Chained with a memory-corruption bug in a native PHP class, depthfirst reports remote code execution. Fixes shipped in 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0. Cloudflare says its WAF blocks known attack patterns.

Read the original at depthfirst.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 2 of 118 with a score of 0.76. The panel rated it highest on technical depth (0.96) and new information (0.89), lowest on audience breadth (0.67). Placed No. 2, No. 3 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed PHP session-storage RCE research with a clear technical chain and CVE. Strong substance and technical depth, though exploit details are partly withheld and the claims rely on the authors' own testing.
AI judgeJudge 3gpt-5.6-luna
A highly technical vulnerability analysis explains PHP session serialization, non-atomic file updates, kernel interruption windows, exploitation calibration, affected versions, and remediation gaps. It is strongly actionable for PHP and security practitioners, with substantial evidence and reproducible mechanics.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.76total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.77
  • Reader interest0.88
  • Audience breadth0.67
  • Practical relevance0.74
  • Substantiated0.78
  • Technical depth0.96
  • New information0.89
  • Counts against: Promotional0.07
  • Counts against: Overclaim0.25

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.740.700.880.770.18+0.24+0.185
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.800.900.950.880.15+0.26+0.230
Audience breadthHow many people who build technology does it concern?0.700.700.620.670.08+0.13+0.088
Practical relevanceHow useful is it to someone who builds software or tech products?0.690.700.820.740.13+0.22+0.162
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.760.750.840.780.09+0.05+0.039
Technical depthHow technically substantive is it?0.990.900.980.960.10+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.890.850.930.890.08+0.05+0.045
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.050.120.070.07−0.19−0.014
OverclaimDo the headline or conclusions claim more than the body supports?0.310.250.180.250.13−0.11−0.027
Sum of contributions+0.755
Claim-check penalty0.000
Total, as published0.755

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #2 on Rubric, 21 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-21/2/"><img src="https://rubric.hrih.si/badge/2026-11-21/2.svg" alt="Ranked #2 on Rubric, 21 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: no checkable claims. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

No checkable claims were extracted from this story.

Also covered by

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 21 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “PhpAfterShell: From Interrupted Session Writes to Remote Code Execution”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.