> As a bonus, they also posted a reverse chain: popping Edge from calc [0].
What the hell is going on there? Apparently they are spawning new and new and new instances of calc.exe until one random (?) instance is vulnerable to some sort of attack, then they inject some shellcode into it from outside, and manage to trigger it by inputting "1"s until there's an overflow?
I always felt bad about the whole site/browser cross integration that chrome and edge and others do. Now I feel really really really bad about it. Can almost see the marketing team's emails about what features to add, and the developers unwantingly writing the code not expecting such things to open so many holes
I think they very well understand that this code was full of bugs but no one cared. Likely was assigned to some junior who was making an entry into the team/repos as a non-critical task.
And it's hard to judge them: I'd also rather focus on real features.
I guess that explains the questions I had when I was mysteriously logged into Edge. I checked whether Chrome does something similar, and it can, but the setting "Sign in to Chrome when you sign in to other Google services" was set to "Don't sign in", so I'm not sure whether this is the default or not.
> So even if you’ve never created a User Profile in the browser, just visiting www.microsoft.com is enough for Edge to create one and sign you in automatically.
Glad to now have some hard evidence I can reference whenever I bring up my strongly held intuitive opinion of "Microsoft repackaging someone else's browser and adding some extra stuff to it can only make Edge strictly worse"
seconding this. it's even worse for those with executive dysfunction where it becomes too difficult to force one's self to continue taking what is now the long way around. even if you could do it so much better with time and practice.
Oh dear god, at each further chain link I was laughing so hard that my poor cats got disturbed!
This entire chain is nothing but a lesson of shame for Microsoft - if you fork a thing, better be prepared to thoroughly understand and review each corner you touch. Or you might miss important cross-references that you should update but that aren't mentioned in comments by the original developers.
As for the "sign in automatically" BS that both Google and Edge push - that can go and die in a hellfire where it belongs.
If you can understand nuance and context, you would realise the phrase right before that is saying that he's not going to go into details about how navigation itself works in Chrome/Edge, and to watch the presentation from Google itself about those specific details if you are so inclined.
If you then continued on to read the remainder of the article, you would also discover that there was no AI assistance in this research at all.
Same; either put in the work to think it through and show us your thought process and conclusions, or just post your prompts and call it a day and everyone gets to move on.
If you continued to read the article, you would discover that he indeed goes through his entire thought process in building this chain. Including the fact this was done with no AI assistance at all.
it's sort of funny, because before you even get to the line you stopped at, and then assumed that they used ai, you have to read this part:
"Anyway, this is what I built for Pwn2Own Berlin 2026 — a completely handmade, logic-only Microsoft Edge Full Chain, with no memory corruption, and no AI at all!"
No memory corruptions, no heap shenanigans, just pure logic bugs, almost made easy to understand for the reader.
As a bonus, they also posted a reverse chain: popping Edge from calc [0].
[0] https://www.youtube.com/watch?v=Bh1zglq4mLE
What the hell is going on there? Apparently they are spawning new and new and new instances of calc.exe until one random (?) instance is vulnerable to some sort of attack, then they inject some shellcode into it from outside, and manage to trigger it by inputting "1"s until there's an overflow?
Really looking forward to the writeup lol
And it's hard to judge them: I'd also rather focus on real features.
Special casing your domains to be assumed "secure" is exactly how you build vulnerabilities directly into your software.
It's an inevitable result.
Developers aren't aware because they assume a security model where the special casing is disabled.
Wow, this is disturbing on its own
This is disgusting behaviour, RCE chain or not.
This entire chain is nothing but a lesson of shame for Microsoft - if you fork a thing, better be prepared to thoroughly understand and review each corner you touch. Or you might miss important cross-references that you should update but that aren't mentioned in comments by the original developers.
As for the "sign in automatically" BS that both Google and Edge push - that can go and die in a hellfire where it belongs.
But what hapens when there's no Javascript interpreter, i.e., not the so-called "modern" browser
And when the OS is not Windows
The so-called "modern" browser _is_ a "logic bug". It's multiple layers of stupidity if "security" is a goal
> I won’t go into too much detail in this post, because I think in this era, you can just ask your agents to fill in the details :)
If you then continued on to read the remainder of the article, you would also discover that there was no AI assistance in this research at all.
In fact, a problem with LLMs is that they consistently write more than I want to read.
"Anyway, this is what I built for Pwn2Own Berlin 2026 — a completely handmade, logic-only Microsoft Edge Full Chain, with no memory corruption, and no AI at all!"