frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Tell HN: 2x PHP RCE CVEs with CVSS 10.0 Incoming

204•petecooper•17h ago•32 comments

Ask HN: How to deal with shipping AI-written code you don't understand?

592•rzk•1d ago•709 comments

What should I use instead of Firefox on Android?

2•trystrawberries•2h ago•3 comments

Ask HN: Does anyone else just want to disconnect from everything?

4•lualover•3h ago•4 comments

Ask HN: Is Wikipedia going to be obsolete soon?

2•piratesAndSons•4h ago•3 comments

Ask HN: My Gemini bill shot up suddenly to 2500 USD in one day

8•kinj28•15h ago•3 comments

Ask HN: Dark mode for HN please? (2026)

22•Stitch4223•1d ago•11 comments

Ask HN: Time to read those programming books?

4•blinkbat•14h ago•9 comments

Ask HN: How to get the most intelligence out of your agents?

9•thechairman12•1d ago•16 comments

Ask HN: Can LeetCode (or similar) keep critical thinking sharp in the AI era?

5•ML0037•17h ago•2 comments

GCP Europe-West2 Outage

30•jack7e•1d ago•12 comments

Ask HN: What do you hate the most about GitHub Actions?

2•Bnjoroge•17h ago•1 comments

Ask HN: Are there any programming positions that are safe from AI?

4•marcAKAmarc•17h ago•6 comments

Ask HN: What have you built privately with AI that you'd like to share?

7•erelong•1d ago•21 comments

Ask HN: Do you know Bitbucket are chaning their SSH endpoints?

3•mcrmonkey•1d ago•1 comments

Ask HN: How do you deal with AI output of your boss?

18•okr•3d ago•16 comments

AGI-S – an AI platform I'm building

2•smitsjoshi•8h ago•1 comments

CPU-native. Deterministic. O(1) processes. – the Old New Coolness

2•KathiaGatterer•1d ago•1 comments

Ask HN: What happened to open weights models?

5•sparse-Matrix•1d ago•2 comments

Ask HN: Why HN dosen't have bot problem?

7•solarpunk_enthu•1d ago•8 comments

Revolut down – Global ATM withdrawals and bank transfers failing

15•TomAnthony•1d ago•7 comments

Tell HN: I picked up knitting while waiting for my AI agent to complete

9•amelius•2d ago•2 comments

Ask HN: What's your SSH terminal workflow like?

2•otherayden•1d ago•7 comments

Ask HN: How do you cap what your coding agents can spend?

3•Twirled•2d ago•1 comments

Ask HN: Bring-your-own-AI hardware

2•flying_sheep•1d ago•0 comments

Ask HN: Any good technical podcasts to listen to while driving?

4•0-bad-sectors•1d ago•3 comments

Ask HN: Why can't Ukraine use LoRA instead of Starshield?

4•xrd•1d ago•5 comments

Tell HN: Getting spam after commenting on monthly Who's Hiring posts. Who else?

6•yosito•1d ago•1 comments

Ask HN: Beyond traces, how do you know your agent did the job?

5•rstagi•1d ago•3 comments

Talk like Paul Dirac – fewer words is better

12•asen•3d ago•19 comments
Open in hackernews

Tell HN: 2x PHP RCE CVEs with CVSS 10.0 Incoming

202•petecooper•17h ago
A reliable source has indicated an announcement is scheduled for 22 October 2026 at 18:00 CEST regarding 2x PHP RCEs with a CVSS score of 10.0.

I have no evidence beyond "source: trust me, bro", but if you're running PHP in production, be ready to update as a priority.

These CVEs reportedly relate to remote code execution in all affected PHP versions from PHP 5 onwards.

These are the two reserved CVEs for the reported upcoming announcement:

CVE-2026-109618

CVE-2026-109619

Comments

SchizoDuckie•13h ago
Well great thanks. I need details now. Where, core? Extensions? What config?

My guess is on some request filtering thing

dwm•10h ago
Details are due for disclosure at 1400hrs UTC tomorrow. That timeline may yet change.
reddalo•10h ago
Yes, it's on core. All versions from PHP 5 onwards. Only PHP 8 will be patched.
joshuat•8h ago
So a few million WordPress sites are just going to be overnight targets.

Although I guess that's not a dramatic change in the status quo.

Yiin•7h ago
surely not only 8, that would be insane
rpeden•6h ago
Everything before 8.2 is past EOL.
brazzy•40m ago
This is serious enough that EOL should not matter. Of course, if someone is still running PHP 7 or even older, they're probably not updating anyway.
ShowalkKama•10h ago
Those CVEs refer to vulnerabilities in wordpress plugins (not php) and the vulnerabilities are not RCEs.

Am I missing something?

https://nvd.nist.gov/vuln/detail/cve-2026-9618 https://nvd.nist.gov/vuln/detail/cve-2026-9619

dylanpyle•10h ago
It sounds like the upcoming ones are 2026-109618/109619, not 9618/9619
ShowalkKama•10h ago
I even double checked, I'm so blind.
HotGarbage•10h ago
https://www.php.net/archive/2026.php#2026-10-20-1
reddalo•10h ago
Official statement released by PHP: https://www.php.net/archive/2026.php#2026-10-20-1

Statement by CERT-EU: https://cert.europa.eu/publications/security-advisories/2026... :

>Where immediate patching is not feasible, organisations should consider isolating internet-facing applications from public networks until a fix is available.

It seems serious. Well, good luck isolating all PHP applications from the public internet...

unreal37•9h ago
This was supposed to be embargoed.

So your reliable source can't keep a secret.

petecooper•1h ago
Yeah, she lied when I asked if it was under responsible disclosure/co-ordinated disclosure -- otherwise I wouldn't have posted it!
kevinday•8h ago
Quick correction to the text above, PHP says the patch/announcement will be available Wednesday, 21 October 2026 at 14:00 UTC.

https://www.php.net/archive/2026.php#2026-10-20-1

gnabgib•6h ago
Yes it's now Wednesday, but Thursday was originally correct. Because of this HN post, it's been moved up to tomorrow.
archon810•7h ago
Here's the alleged demo video. It's called php2shell https://x.com/k_firsov/status/2112641845926989944 and it's scary as hell.
phab•7h ago
Tweet allegedly showing exploit at work:

https://x.com/k_firsov/status/2112641845926989944

(video). Yikes

koolala•4h ago
This video is iconic
1over137•4h ago
This seems to work without an X account: https://nitter.app/k_firsov/status/2112641845926989944
potaytopotahto•6h ago
Looks like details about the exploits have already leaked on twitter, if the info is correct then it can be mitigated by setting session.upload_progress.enabled = Off until you get the opportunity to update
rbarden•6h ago
The person who posted the main video that's getting shared confirmed this as well: https://twitter.com/k_firsov/status/2112718728232329240
4lun•2h ago
Not enough apparently

> The PHP 8.6 release manager is on Reddit saying this can’t be fixed with ini settings alone, and needs PHP to be patched

https://x.com/johnplaysdf/status/2112737802379047099?s=46

> INI settings alone won't protect you. You need to patch PHP.

https://www.reddit.com/r/PHP/comments/1xb2utu/comment/phyu5m...

lol768•6h ago
There comes at point at which it is better for everyone to just disclose the details and pursue Full Disclosure. I think we reached that point hours ago.

It has been incredibly frustrating watching Twitter and that (potentially, I don't know how reliable the leaks are) being a better information source than anything else, at least so that those of us hosting stuff ourselves can try and explore if there are any defensive measures that can be put in place in lieu of any actual fixed builds being released.

I suspect this is already being actively exploited now.

https://x.com/J4ck3LSyN/status/2112703096443097263

They've now posted a proof of concept as well.

jwitthuhn•6h ago
Seems like some of the people engaging in "responsible disclosure" were not very responsible and it leaked out.

With that info public they do really need to just release the fix, assuming that tweet is accurate.

edit: Mitigation for impacted versions is to set `session.upload_progress.enabled = Off` in php.ini

lol768•5h ago
> edit: Mitigation for impacted versions is to set `session.upload_progress.enabled = Off` in php.ini

I think this is only partial mitigation: https://x.com/Dinosn/status/2112717168349712734

I have additionally followed the advice to just ban multipart uploads before the request even touches PHP (luckily my app doesn't use them at all). I do now know if this conclusively resolves it.

Webfiletools_de•5h ago
One gotcha for anyone applying this tonight: on a lot of Debian/Ubuntu-style setups the CLI and PHP-FPM read different php.ini files (for example /etc/php/8.x/cli/ vs /etc/php/8.x/fpm/), so "php -i" from a shell can show it Off while the web side still has it On. Check it through a phpinfo() page or the FPM binary itself, and remember to reload php-fpm afterwards. On shared hosting where you can't touch the main ini, it should be settable per directory in .user.ini, but that file is cached for a few minutes by default, so give it time before testing. And as others said, treat it as a stopgap until the actual patch lands.
lioeters•6h ago
This vulnerability has already been reproduced by a third party with LLM assist. And of course they posted the details on Twitter - and someone else posted the link here just now. So the cat's out of the bag.

That means roughly 70% of all websites (WordPress, Laravel, Drupal, Joomla, Magento) are currently open to remote code execution. About half of that is running an older PHP 5 and 7 that apparently will not receive the urgent security patch.

> Two heap use-after-free primitives in PHP's `session.upload_progress` handler

Guess it's time to rewrite PHP in Rust. Claude, make no mistakes, you can do it!

coderdiaz•5h ago
The full details will be available on 8:00 AM at Mexico City
kevbo823•3h ago
If you don't do local file include (LFI) esp. from a $_GET or $_POST then to what degree would the site be impacted?
MuteXR•31m ago
...100%?
vincent_s•2h ago
Two things you can do now:

1. Turn off session upload progress

2. Block multipart requests at the web server

More info: https://www.vincentschmalbach.com/cve-2026-109618-and-cve-20...