PHP-FPM request smuggling allows unauthenticated remote code execution
Comments on “PHP-FPM request smuggling allows unauthenticated 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
A PHP security advisory describes a PHP-FPM request smuggling flaw, fixed in the 19 November releases (8.5.13, 8.4.28, 8.3.37, 8.2.36). Unread php://input bytes can be parsed as a forged FastCGI request, letting an unauthenticated attacker run PHP as the worker. It requires persistent backend connections, such as nginx fastcgi_keep_conn, and an app that opens php://input without reading it fully. The affected-since-5.6.0 claim rests on code inspection. Until upgrading, disable connection reuse. LSAPI is affected by desynchronisation only.
Why it ranked
No. 1 of 140 with a score of 0.80. The panel rated it highest on new information (0.94) and practical relevance (0.92), lowest on audience breadth (0.67).
- AI judgeJudge 2claude-haiku-5-5
- Detailed, specific advisory of unauthenticated RCE in widely used PHP-FPM with a clear mechanism, affected configs, and mitigations; highly actionable for builders running PHP behind nginx or Apache.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, actionable advisory describing unauthenticated PHP-FPM request smuggling to RCE, affected configurations, exploit mechanics, limitations, and mitigations. It is highly relevant to operators and developers, with only modest uncertainty about demonstrated scope.
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.80total under rubric v2.3
- Significance0.77
- Reader interest0.88
- Audience breadth0.67
- Practical relevance0.92
- Substantiated0.76
- Technical depth0.91
- New information0.94
- Counts against: Promotional0.03
- Counts against: Overclaim0.21
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.70 | 0.72 | 0.90 | 0.77 | 0.20 | +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.76 | 0.90 | 0.98 | 0.88 | 0.22 | +0.26 | +0.229 |
| Audience breadthHow many people who build technology does it concern? | 0.65 | 0.75 | 0.62 | 0.67 | 0.13 | +0.13 | +0.088 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.93 | 0.90 | 0.92 | 0.92 | 0.03 | +0.22 | +0.202 |
| 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.54 | 0.85 | 0.88 | 0.76 | 0.34 | +0.05 | +0.038 |
| Technical depthHow technically substantive is it? | 0.96 | 0.85 | 0.90 | 0.91 | 0.12 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.95 | 0.99 | 0.94 | 0.10 | +0.05 | +0.047 |
| 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.05 | 0.03 | 0.01 | 0.03 | 0.04 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.41 | 0.15 | 0.08 | 0.21 | 0.33 | −0.11 | −0.023 |
| Sum of contributions | +0.804 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.804 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-11-20/1/"><img src="https://rubric.hrih.si/badge/2026-11-20/1.svg" alt="Ranked #1 on Rubric, 20 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenVersion
The vulnerability was introduced with lazy php://input handling in PHP 5.6.0.
The article gives no link or citation for it.
The article says “The issue was introduced with lazy php://input handling in PHP 5.6.0”
The source says No source to compare with.
No source givenCausal conclusion
During request shutdown, PHP incorrectly treated the existence of a php://input stream as evidence that the body had been handled, skipping cleanup that discards unread input.
The article gives no link or citation for it.
The article says “PHP incorrectly treated the existence of this stream as evidence that the body had already been handled and skipped the normal cleanup that discards unread input”
The source says No source to compare with.
No source givenCausal conclusion
An unauthenticated attacker can make leftover body bytes form a separate FastCGI request in PHP-FPM, bypassing front-end routing and executing attacker-controlled PHP code with worker privileges.
The article gives no link or citation for it.
The article says “an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker”
The source says No source to compare with.
No source givenCausal conclusion
If the attacker knows the path of an existing PHP script, they can set allow_url_include=1 and auto_prepend_file=php://input so the forged request's input is executed as PHP.
The article gives no link or citation for it.
The article says “they can set allow_url_include=1 and auto_prepend_file=php://input, causing the forged request's own input to be executed as PHP”
The source says No source to compare with.
No source givenGeneralization
Exploitation requires a front end with persistent backend connections and an application path that opens php://input without reading it fully; standard nginx and Apache configurations that close the FastCGI connection are not affected by the demonstrated attack.
The article gives no link or citation for it.
The article says “Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated PHP-FPM attack”
The source says No source to compare with.
No source givenGeneralization
The attack needs no memory corruption, knowledge of memory addresses, or race condition, and works with a single request.
The article gives no link or citation for it.
The article says “The attack crosses the HTTP-to-PHP backend trust boundary using a single request. It does not require memory corruption, knowledge of memory addresses or a race condition”
The source says No source to compare with.
No source givenGeneralization
For LSAPI, the shared cleanup error can desynchronise the request stream, but the advisory does not establish arbitrary code execution through LSAPI.
The article gives no link or citation for it.
The article says “this advisory does not establish arbitrary code execution through LSAPI”
The source says No source to compare with.
No source givenVersion
The affected code has been present since PHP 5.6.0, based on code inspection.
The article gives no link or citation for it.
The article says “The affected code has been present since PHP 5.6.0. This is based on code inspection”
The source says No source to compare with.
Also covered by
Elsewhere
Elsewhere: HN 5 pts, not on front page
Recorded for context only, checked 20 Nov 2026, 05:47 UTC. It played no part in the ranking.