Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
PS5 Jailbreaking       Thread starter PSXHAX       Start date Jan 15, 2022 at 1:32 PM       34,525       112      

Is it too soon for a public PS5 Jailbreak?

  • Hell no, bring it on already!

    Votes: 1,200 54.5%
  • Yes, many can't get a PS5 yet!

    Votes: 1,002 45.5%

  • Total voters
  • Poll closed .
Not open for further replies.
Previously the PlayStation 5 Scene saw a PS5 WebKit Vulnerability alongside implementation of a PS5 Userland Exploit for 4.03 PS5 Firmware, which was followed by PS5 Debug Settings & Root Keys Obtained with scene developer @Mathieulh openly stating on Twitter that "Kernel execution has been achieved since week 1" around when the AMD Server Vulnerabilities were disclosed as @zezu420 (aka Znullptr) confirmed the pOOBs4 ExFAT Bug also affects PS5 while BTC Donations set up allowed the lead developer to get a PlayStation 5 console to fully implement the KeXploit on... exemplified by today's PS5 4.03 Kernel Build String image below from Znullptr (aka dmiller423) on Twitter! šŸ„³

:idea: Those who would like to support his continued development work may do so via BTC Donations, GoFundMe, becoming a Github Sponsor or Patreon. :lovewins:

:alert: Before collectors of PS5 Game Dumps in the PS5Scene get too excited, there's currently no ETA for a public PS5 Kernel Exploit release... but at least knowing it works on 4.03 and below may help those considering updating to Sony's current 4.50 PS5 Firmware make a wise decision not to update for the time being. ;)

:poll: Be sure to vote in our current Site Poll: Is it too soon for a public PS5 Jailbreak?

Finally, we'll keep the PlayStation 5 (PS5) Jailbreak Status page updated as things progress with some related articles (sorted by date, with the oldest first) and Tweets below:
r179926/releases/04.03 Oct 13 2021 08:48:08
PS5 4.03 Kernel Build String by Znullptr, No ETA for PS5 Kernel Exploit.jpg


Red Eye Jedi

VIP Member
There is literally no reason to not release that hack. It will be niche like the PS4 1.76 but lead the way for the 4.05+ exploits we had.

If there was any possibility it working on higher firmware I say hold on to it. But it was patched before this was even publicly known.


@andisheegold the vulnerability is patched but I was talking about the exploit mitigations/security features to stop us turning a vulnerability in to a full exploit.

From the new writeup today for example we can see Clang CFI/Control flow integrity which is a security method to stop vulnerabilities becoming exploitable was bypassed. This creates a list at compile time of what each part of the program can talk to and stops you talking outside of this list, which is what exploits would do.

A couple of years ago it was shown there were a few exploits against this extra security method, one of which was used (overwriting the stack/memory where the list is stored... kinda) for this new PS5 PoC.

Now Sony knows this was done, they might try recompiling the executable again with different flags to protect against this technique in future versions. That is a crude example of what I was getting at. Patching/changing security methods rather than core executables that might get exploited.

It depends on what and how it was bypassed. I'm not even sure if it would matter in this case saying all that though. I think most exploits will be investigated using lower level firmwares unless newer FW can be checked against previous ones to see the differences/what was patched and exploits reversed from found patches.

Glad we have this userland sploit though. More people looking at it might find ways to get around the XOM memory protection.

Thats how I understand it anyway


If gow Ragnar or forbidden w, or even gt7, coming it will be on newer version than 4.03.

And I just got my ps4 after long struggling, good luck for you ps5 owner, really happy for you guys :spsbuttoncolor: :bananaman13:
Not open for further replies.

:fire: Latest Help Topics