Claudio Criscione

Security Robot Overlord @ Google.
Vulnerability Management

@paradoxengine.criscio.net
@[email protected]

[Claudio Criscione @paradoxengine]

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

[m0z @LooseSecurity]

Seeing https://t.co/OLRcUadEGX getting registered one week ago is a little concerning 🙈😅

[Claudio Criscione @paradoxengine]

I am, in fairness, terrified of ninjas.

[thaddeus e. grugq @thegrugq]

Fear of 0day is like being terrified of ninjas instead of cardiovascular disease.

[Claudio Criscione @paradoxengine]

@julianor Hopefully I push it all in tsunami open source early next week

[Claudio Criscione @paradoxengine]

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

[Claudio Criscione @paradoxengine]

@julianor Bunch of ways to trigger the curl path on common apps, I think by now they are mostly known but it's just all over. Few appliances (this is bound to be fun), all reported. A number of internal things. Some endpoint-side things (I don't think that exciting)

[eu/acc @euacchq]

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/

[Claudio Criscione @paradoxengine]

@julianor Yep! But for callback stuff (WordPress Drupal etc etc etc) that goes through curl you need to get the trigger right. I think I've got a decent library, hopefully will push to tsunami next week with an update to the callback server!

[Arian van Putten @ProgrammerDude]

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.

[caveeroo @caveeroo]

HTTP2Shell (CVE-2026-111497) is exploitable outside Node. Unauth RCE against a pinned vulnerable Docker Official Image for WordPress via /xmlrpc.php. One inbound https://t.co/RkaXqtLpZV, ASLR on, no leak or cross-request grooming.

PoC: https://t.co/jmdKprFgKk

[remot3 @_remot3]

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 :)

[AndrewMohawk⁽ⁿᵘˡˡ⁾ @AndrewMohawk]

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

https://t.co/iQy3R88cnx

[Scott Piper @0xdabbad00]

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.

[Juliano Rizzo @julianor]

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. 🥦

[Thomas H. Ptacek @tqbf]

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.

[Matthew Prince 🌥 @eastdakota]

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.

[Patrick McKenzie @patio11]

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.

[lauren @poteto]

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 (https://t.co/7fzYZV8LGH). 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 (https://t.co/gTBZx7pl14) 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

[Claudio Criscione @paradoxengine]

@SnapperClapper1 @TipOfTheBanana Possibly? The collective rage of Italians witnessing broken spaghetti must generate some energy and some of that will help with cooking?