
I think my new rule is that if you say you formally verified some complex software and don't say anything about all the things you had to fix to make the proof go through, then I simply don't believe you

Security Robot Overlord @ Google. Vulnerability Management @paradoxengine.criscio.net @paradoxengine@infosec.exchange

I think my new rule is that if you say you formally verified some complex software and don't say anything about all the things you had to fix to make the proof go through, then I simply don't believe you

I was looking at the (ai generated) detector I wrote for the brotli thing and that level of complexity would have taken many weeks...

Seeing apache2shell.com getting registered one week ago is a little concerning 🙈😅

I am, in fairness, terrified of ninjas.
Fear of 0day is like being terrified of ninjas instead of cardiovascular disease.

Ladies & Gentlemen, we have managed to get the @EUCouncil ' EU Inc files. The ones that matter. The ones where we see the position of Each Member state: including who pushed the notaries' agenda. Buckle up and Repost. 🍿 Now if you are from those Member States, make some noise. Directly or through associations, politicians. Enjoy the thread 🧵 1/

Man the brotli thing really is way more widespread than I had realized. Lots of new detectors coming in the Tsunami scanner.

Hear me out. Just spin up an agent for each dependency you have and have it be the babysitter for that dependency. It is a surprisingly effective pattern. It only opens PRs when I’m actually vulnerable and can even find vulns before they are lifted from embargo.
fyi dependabot time to open a PR is median 8 days

HTTP2Shell (CVE-2026-111497) is exploitable outside Node. Unauth RCE against a pinned vulnerable Docker Official Image for WordPress via /xmlrpc.php. One inbound pingback.ping, ASLR on, no leak or cross-request grooming. PoC: github.com/caveeroo/cve-2026…

The danger of HTTP2Shell is very real. The libbrotli 🥦vulnerability affects a wide range of software, patch now (CVE-2026-111497) We've achieved unauth RCE in Docker's official WordPress image abusing the well known /xmlrpc.php endpoint, we call it the pingback of hell :)

Apparently tweeting “I have a working PoC” creates a small obligation to explain how the thing works 😅 So here it is: both PHP bugs, the memory leaks, the ASLR bypass, worker pinning, and how I eventually got to execution andrewmohawk.com/2026/10/26/…
Its me, I have a working PoC with the infoleaks to bypass ASLR. It took a lot of prompting and re-iterating to find those, tested against PHP 8.5.11 x86_64 with with all defaults and tested over the Internet

Interesting post showing the wait times between when a fix comes out, and how long you have to wait for various installers, containers, and other resources make it available for you to use.
Ruby 4.0.9 shipped security fixes last Friday. Ruby core's Docker image: 8 minutes Community ruby Docker image: almost 16 hours Google Cloud: ~3.5 days AWS Lambda: still waiting How fast can you actually patch Ruby? 👇 paagman.dev/how-fast-can-you…

IMHO, the Brotli bug (think zlib 20 years ago) is a bigger deal than PHP2Shell and all the "oooh, AI found it! AI found it!" hype. Node2Shell is a terrible name. I’m calling it Broccoli. 🥦

This is the first time I've ever seen a site do this, the obvious simple response to a disclosure of a vulnerability without a fix: sacrifice availability to preserve safety. This option should be why we do full disclosure.
There's a severe bug in PHP that is apparently being exploited already. To protect everyone's data, I have taken Pinboard offline until patches are released tomorrow. I'll get the site back up as soon as I can after that happens.

Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.

A few of us have been predicting saturation of adversarial contact points for a while, but this is first set of good graphs I’ve seen of it. Imagine it will take owning agencies a very substantial amount of time to realize what is happening.
To give an indication of the problem here's a chart of 12 government agencies around the world and numbers of applications / appeals / complaints etc... The dotted grey line is when ChatGPT was invented.

volume does matter look, i get it. if you were an engineer before agents came along, you're rightfully skeptical about lines of code and number of PRs being used as a metric for any kind of productivity. and i agree! or at least, i used to. for ease of explanation i will talk about this from the perspective as being an engineer on a large team of at least 50. volume didn't matter before because we focused on impact. you could have high impact even with a few PRs: for example you could make a one line config change and save the company millions of dollars. but before agents, the times where i saw volume come into the conversation were for the outliers. on the negative end you might have someone who is struggling to perform, on the other end you might have someone who was a "coding machine" archetype. a coding machine was someone who could just lock themselves in a room and emerge with a stack of PRs that solve a huge number of problems. so volume did matter, but only at the tail ends of the distribution, and combined with impact. if you've ever worked at a large tech company before, you'll get what i mean. the thing about agents is that big tech co problems are now small-medium co problems as well. how do agents change this calculus? well, everyone now has the ability to become a coding machine. you have incredibly capable frontier models that can write code better than any of us, at a rate much faster than we can. in this world, if you're still producing the same number of PRs as before, why wouldn't you pause to wonder why you're not being more productive? alien intelligence is here, and yet you can't outship a human coding machine? this brings me back to why i keep talking about trust (x.com/poteto/status/21020504…). if you haven't put in the work to trust your agent's output, it is very difficult to scale up your productivity. and yes, this approach does require more tokens, but i think about this in terms of cost per intelligence. before agents, this cost was very high - you needed to hire many software engineers with high 6 figure salaries to do the work. tokens are still expensive today, but are likely to get cheaper over time (x.com/theo/status/2107924138…) factoring in the cost of intelligence. what looks exorbitant today will likely be affordable in 6 moths to a year. a single engineer with agents can do the work of tens if not hundreds of engineers, at a fraction of the cost. the reality that i don't think has hit yet is that job of the software engineer has truly changed. our job is not merely to produce software any longer (well tbh it was never only about the code, but bear with me for the sake of the explanation), but the machine that writes the software. this idea of a software factory, or a Michelin kitchen as i like to call it, is still a topic of research. and it's the type of stuff i like to share, not to flex, but to show you what's possible when you put a lot of rigor into using agents at scale
Can someone help me understand how shipping 100s PRs a day makes sense? Why do you need to ship so many PRs in the first place? I might just not be AI-pilled enough to understand the need for it yet, so I’m genuinely trying to understand it.