Fw 10.00
Wow Sony that was Quick 2 days to fix it after it had been reported for 6 months.
Now that Sony fixed I can really start to release as much information as I want without worrying about it legally and it's pretty easy to say don't update 2 10.00 unless you wanna miss out
Debty
23 posts
Joined August 2024
- Someone modified my code idk what he did but he just made it trigger an error everytime it's a system error at that it seems like he's trying to make it copy a payload.bin github.com/seregonwar/Ove… This might be a first for Sony an exploit that releases for the latest frimware
- Never though id wake up to my exploit suddenly becoming public news so I guess yeah Congrats on finding it I have all the commits if you need them. The one I posted publicly on GitHub might not be useful never tested as much as the others but I can say it bricked my test PS5
- 📢 Discovered a WebKit memory leak affecting PS5, reported to Sony but ignored.Not a jailbreak just a userland issue. Sharing for educational purposes to gather more data and prompt a fix. debvt.github.io/Wm/ Please be careful works all the time 9.60 #PS5 #Exploit #0day
- Replying to @SeregonWarNo problem it's all yours if you need any more docmantion I'd be happy to help
- Replying to @idebtyAnd It never got fixed reported it but never got fixed works idk till 9.60? 9.40 some high firmware like that. I've taking a break for a while focusing on more important stuff. If you try it and brick your system I'm not liable to any damage caused or done by the exploit
- Idk bro Sony is probably angry at me or smth but hey I'm well within my rights to do so they got more then enough to fix it (6 months) but they didn't
- Replying to @idebtyLiability Warning Im not liable to any damages caused by trying this exploit it has been found to somehow brick system files at random chance if you try this and brick your device then im not liable to any damages caused by it Be Cautious Try at your own risk
- Replying to @ntfargoString exploit isn't actually an Exploit just like a memory exhuster I've made and it isn't actually viable instead I've added an option called latest iteration which has the source in the readme
- Replying to @m0ur0neI appreciate the input from AI analysis, and I understand that it may have initially classified this as a memory exhaustion issue. However, my real-world experience tells a different story. When I ran this code on my device, it didn’t just eat memory—it caused system corruption.
- Replying to @SeregonWar and @realTrendSailorI'm working on a full docmation You will find it in the docs folder when ever it's ready Keep an eye out at my docs folder 👀

