Ed Grosvenor retweeted
if you're running scale-to-zero on Laravel Cloud and feel like your app wakes up too often from random bot scans, ping me
we're cooking something up and are looking for data/testers
tell your friends
Ed Grosvenor retweeted
Not a good month to be a C bro 😞
terminal2shell.com
We’ve published a post-mortem on our response to the October PHP and Node.js security releases, covering the in-place patching of Laravel Cloud, the impact on Forge, Envoyer, and Vapor, and what we’re changing → laravel.com/blog/php-nodejs-…
Ed Grosvenor retweeted
And the reason there's anything to report each week: the PHP Foundation funds more than half of ongoing php-src commits.
If you use the language, consider donating — or guilt your employer into it.
opencollective.com/phpfounda…
Ed Grosvenor retweeted
Zug, 29 October, Xelon offices. Doors open at 18:00, first talk at 18:30. If you haven’t RSVP’d yet:
luma.com/sw57o2f1
Ed Grosvenor retweeted
Ruby’s turn 😅
Remember the GitLab bug? Well now it moved upstream into Ruby.
Multiple 10.0 CRITICAL exploits.
Patch now 🚨
Happy Friday 🤠
ruby-lang.org/en/news/2026/1…
Ed Grosvenor retweeted
Didn’t want to shill my stuff during the chaos or in my Security Notices, but now things have calmed down (I hope!):
I do Laravel & PHP Security Audits & Pentests. If PHP2Shell has you wondering what’s hiding in your own apps, I can help.
valorinsecurity.com
Ed Grosvenor retweeted
I'll be the first to admit I'm mediocre at exploit development, but I am in contact with enough extremely talented exploit developers to say this for certain:
Anyone claiming they were "easily" able to generate a working php2shell exploit with AI is either:
a) a world-class exploit developer with an extreme case of imposter syndrome.
b) currently looking at some very confident-sounding but wrong LLM output.
I'm rather certain it's the latter based on the number of AI-hallucinated exploits I've seen posted on GitHub. Threat actors are also blasting my honeypot network with "php2shell" exploits that not only don't work, but aren't even within 10,000 miles of anything to do with how the exploit actually works.
I've seen the same technique from the attached image in multiple alleged "php2shell exploits", including one on GitHub with over 100 stars. Problem is, it's not php2shell, nor is it even a vulnerability at all. It's a technique known as "session poisoning", which can be leveraged to exploit local file inclusion (LFI) vulnerabilities in PHP apps (not PHP itself).
The only thing it has in common with CVE-2026-109618/CVE-2026-109619 is they both use the "PHP_SESSION_UPLOAD_PROGRESS" feature. And mitigation advice for both issues reference setting "session.upload_progress.enabled" to "Off".
People are shoving loose details of the vulnerability into LLMs, the LLMs are keying in on the "PHP_SESSION_UPLOAD_PROGRESS" string, then generating session poisoning code that has nothing to do with the actual CVE. And because the people doing this have absolutely no idea what they're doing, they're confident enough to post their "proof of concept exploit" to GitHub and share it on social media.
So if you see people talking about "session poisoning + LFI" it's likely their LLM hallucinated an exploit based on a 2018 blog by Orange Tsai talking about a local file inclusion attack vector.
What's even worse is that "security researchers" are then using LLMs to triage these exploitation attempts, falling victim to the same hallucinations, then confirming there is ongoing mass-exploitation (there currently isn't).
The actual real exploit is very difficult to exploit, and so far I've not seen anyone successfully get it working on more than a handful of PHP version with highly-specific configurations.
LLMs are useful tools in the hands of skilled professionals, but for others, they're often just a Dunning-Kruger accelerator.
Ed Grosvenor retweeted
How to patch the PHP CVE-2026-109618 and CVE-2026-109619
Full guide on Debian, Ubuntu & RHEL together with steps for PHP-FPM, FrankenPHP & mod_php installs
Stay safe out there PHP friends!
Keeping this updated as more packages become available
ma.ttias.be/php-cve-2026-109…
Ed Grosvenor retweeted
PHP sites behind Cloudflare already have an initial set of WAF rules deployed for the known exploit vectors in these vulnerabilities. The rules are available to all customers, including free.
We are seeing early attacks emerging and are updating mitigations as new vectors show up.
This is a STOPGAP only. Patch as soon as @ThePHPF releases the update at 14:00 UTC today.
arstechnica.com/security/202…
The private keys for these certs are literally the numbers 4, 56, 66, 115, 155, 156, 230, and 237 (life imitates XKCD, again).
We've published multiple advisories affecting the dev server.
The main one is an arbitrary command execution when using some editors or through launch-editor on Windows.
Update now to the patched versions:
- Vite 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4
- Vite+ 1.1.0
Report links 👇🏻
Ed Grosvenor retweeted
Just let Opus to a review of all the Laravel upgrade Shifts for additional automation opportunities. While I used to do this myself, this was a perfect task for AI.
I want to test its changes. But, I don't have any more old apps. Do you? I'll run the Shifts for free!
Ed Grosvenor retweeted
Replying to @aarondfrancis
@aarondfrancis marketing laravel, can I sign you up for sputnikintelligence.com/ (podcast and newsletter data for your agents)? It's good stuff.
Ed Grosvenor retweeted
We got Campfire from @37signals running on @laravel Cloud. It was definitely not built for this, but it didn't turn out as difficult as we thought it would be. Great work by the Laravel team on the Ruby runtime in Cloud. It's going to be amazing!
scalpels.app/lab/experiments…

























