I worked at a fairly big tech co years before the AI boom. People did large scale refractoring across huge code bases back then. With refactoring tools. And properly written robots.
Applying changes to code at scale, opening PRs automatically, basic interaction with human reviewers, making sure tests pass, getting things merged when ready. All that already existed before LLMs. And it was actually reliable and not capable of hallucinating terrible things.
It's like we've forgotten how to automate things without LLMs and openclaw now...
Amaze! Amaze! Amaze! Orange Tsai of DEVCORE Research Team was able to exploit Edge with a sandbox escape! If confirmed, we wins $175K. He's off to the disclosure room to explain how he did it. #Pwn2Own #P2OBerlin
Boom! Valentina Palmiotti wastes no time kicking off #Pwn2Own Berlin in style. She requires just a few second to get code execution on the NV Container Toolkit. She heads off to the disclosure room to provide all the details.
I have published #Diaphora 3.4.0. Now you can install it in IDA by just running this:
$ hcli plugin install diaphora
A 0-click exploit chain for the Pixel 10: When a Door Closes, a Window Opens https://projectzero.google/2026/05/pixel-10-exploit.html
Google replaces your PC mouse with yelling at Gemini
‘reimagining’ the mouse pointer
https://www.youtube.com/watch?v=NSWCWnLMj-U&list=UU9rJrMVgcXTfa8xuMnbhAEA - video
https://pivottoai.libsyn.com/20260513-google-replaces-your-mouse-with-yelling-at-gemini - podcast
time: 5 min 38 sec
https://pivot-to-ai.com/2026/05/13/google-replaces-your-pc-mouse-with-yelling-at-gemini/ - blog post
Hey nerds!
I made a thing!
It's a "chore tracker*, but I took a somewhat unique take on the subject 🙈
It tracks when did you last completed a chore and how close are you to the desired frequency you set for that particular chore.
You can access it here: https://chores-mvp.azurewebsites.net/
There is #privacy policy as well. I hope it will answer most of the questions.
You can self-host it if you're into that sort of things, get it from GitHub: https://github.com/sassdawe/chores
Design goal #1: when popular and eventually hacked leading to user info being leaked @troyhunt should only be able to say: can't add it to HiBP because there is no email address anywhere. ✅
Design goal #2: No passwords because they are bad for security. ✅
Design goal #3: make the users the Most Valuable Partner in doing the Chores. ✅👀
PS: And let me know whether you played around with the Demo and did it spark joy?
The Junkyard Call for Bugs is officially open! 👾
www.districtcon.org/junkyard
For additional information, please reference our Disclosure Guidance doc: lnkd.in/ewjswJyf
And if you missed last years presentations, check them out on YouTube now: https://www.youtube.com/@DistrictCon/shorts
@buherator @christopherkunz @jhr77
Also note that the RedSun author noticed that the vulnerability was fixed, without a CVE
Edit: The RedSun author is wrong. It still works fine
Missing peripheral in QEMU? Adding it yourself is easier than you think.
We hit a wall analyzing CVE-2019-14192 on real Raspberry Pi 3B+ firmware, so we added the missing driver to #QEMU. Register by register, using U-Boot's own source as the spec.
When you hear people abandoning Open Source because of the AI exploit threat, ask them if we should keep our laws secret as well.
Because there is a huge industry of accountants and lawyers specialized in finding exploits in those.
No? Thought so.
Our new multi-model agentic security system brings together more than 100 specialized agents across frontier and custom models to find exploitable bugs, delivering top performance on the CyberGym benchmark.
We used it ahead of Patch Tuesday to help find and fix 16 vulnerabilities. Today we’re announcing that customers can sign up to test it in private preview.
Will you please stop wasting time on Mythos-associated FUD and try to understand that you need to build reliable and dependable software, not stuff which changes weekly, to get security?
Mythos & LLM only bring breadth and depth to automated searching, they find nothing conceptually new, if no-one had come up with buffer overflows there would be no buffer overflows coming out of Mythos.
There will be a flood of issues, as if suddenly thousands of people were dedicated to finding bugs, then it will stop.
It is an excellent chance to ask yourselves "why?" and realise that no, we don't need software like it is being built now, you need software like it was built back when downtime mattered.