← Back to latest articles
Gaming Technology

PS5 firmware 14.10: reported kernel exploit remains research

PS5 firmware 14.10 jailbreak research has reached a major milestone. Developer Gezine has reportedly demonstrated access to Debug Settings on firmware 14.10, suggesting a possible private kernel exploit. Meanwhile, separate open-source research has achieved native userland code execution using Return-Oriented Programming (ROP). However, no complete public jailbreak for firmware 14.10 has been verified.

MAJOR PS5 JAILBREAK RESEARCH UPDATE — NEW KERNEL EXPLOIT REPORTED ON FIRMWARE 14.10

The PlayStation 5 jailbreak community has received significant news following new security research involving firmware 14.10. Developer Gezine has reportedly demonstrated access to the console's hidden Debug Settings menu, while separate open-source research has achieved native userland code execution using Return-Oriented Programming (ROP).
These developments suggest progress in understanding the security protections of Sony's latest PS5 firmware. However, a complete public jailbreak for firmware 14.10 has not been verified.

GEZINE DEMONSTRATES DEBUG SETTINGS ON FIRMWARE 14.10
On 19 October 2026, PS5 developer Gezine reportedly shared a video showing a PlayStation 5 running system software version 26.06-14.10.00 with access to Debug Settings.
The Debug Settings menu is normally hidden on retail PS5 consoles. Access to it can indicate that certain system restrictions have been bypassed, although the demonstration alone does not establish which vulnerability or technique was used.
Reports suggest that a private kernel exploit may be involved. However, the underlying exploit code and technical documentation have not been publicly released.
Gezine also discussed an earlier kernel exploit affecting firmware 13.xx that was reportedly patched in firmware 14.00. According to the developer, this exploit was separate from Relapse.
For now, the reported demonstration is an important development, but it cannot be independently reproduced using a publicly available exploit.

SEPARATE RESEARCH ACHIEVES NATIVE CODE EXECUTION
Another important development comes from developer ZigZagBoi1, who has been conducting open-source security research on PS5 firmware 14.10.
On 19 October, the developer documented successful native userland code execution using Return-Oriented Programming, commonly called ROP.
ROP is a technique that allows researchers to execute operations by combining short instruction sequences already present in a program's memory.
During testing, the researcher used the PS5's thr_create system call to create a functioning thread. The experiment successfully executed multiple ROP gadgets and wrote the hexadecimal value 0xDEADBEEF to a controlled memory address.
This demonstrated that the researcher could perform certain native operations within the existing userland environment.
However, the memory write occurred in userland, not protected kernel memory. It does not establish a working kernel exploit.

HOW THE FIRMWARE 14.10 RESEARCH WORKS
The open-source project uses a Lua 5.1 execution environment accessed through a modified game save.
The research environment provides a network interface on TCP port 9026, allowing experiments to be sent to the console.
The project has investigated several areas of the PS5 operating system, including memory management, system calls, networking and possible information leaks.
Researchers have documented userland memory operations, access to certain system calls and the ability to inspect parts of the process's virtual memory layout.
These capabilities provide a foundation for more advanced security research, but they do not automatically provide elevated privileges.

THE BIGGEST OBSTACLE: KERNEL SECURITY
One of the main challenges facing researchers is Kernel Address Space Layout Randomization, commonly known as KASLR.
KASLR makes exploitation more difficult by changing the memory locations of important kernel components.
To develop certain kernel exploits, researchers may need a reliable way to identify these addresses.
The open-source project has investigated several possible information leaks, but its documented experiments have not established a usable kernel pointer.
Researchers must also identify a vulnerability that allows them to cross the security boundary between userland and the kernel.
Without these additional capabilities, userland ROP execution cannot automatically become a complete jailbreak.

WHAT ABOUT WEBKIT RESEARCH?
A separate project maintained by pastawithpesto is investigating the PS5's WebKit environment on firmware 14.10.
WebKit is the browser engine used by several applications and web-based interfaces.
The project has examined browser behaviour, memory corruption and possible exploitation techniques.
However, triggering a crash or memory corruption does not automatically provide reliable code execution.
A complete exploit would require additional techniques to control execution and overcome the browser's security restrictions.
The publicly documented research does not establish a complete WebKit-to-kernel jailbreak chain.

WHY FIRMWARE 14.10 IS IMPORTANT
Earlier PS5 jailbreak developments, including Relapse and Byepervisor Reborn, demonstrated important weaknesses affecting supported firmware versions.
Relapse provided a public kernel exploitation route for firmware versions reported to range from 7.00 to 13.60.
Byepervisor Reborn later introduced public hypervisor research supporting firmware 13.20 and 13.60.
However, security changes in newer firmware versions have affected the compatibility of these techniques.
The Relapse kernel vulnerability was reportedly patched in firmware 14.00.
Researchers have also reported changes affecting earlier hypervisor exploitation techniques in firmware 14.10.
Consequently, existing jailbreak methods cannot simply be assumed to work on the newer firmware.
A reproducible kernel exploit for firmware 14.10 would therefore represent significant progress.

USERLAND VS KERNEL VS HYPERVISOR ACCESS
Understanding the different levels of PS5 security is important.
Userland access allows code to execute within the permissions of an application or process.
Kernel access provides greater control over operating system functions, memory and security restrictions.
Hypervisor access reaches an additional protection layer responsible for protecting important parts of the system.
A researcher can achieve userland code execution without obtaining kernel access.
Similarly, a kernel exploit does not automatically bypass hypervisor protections.
This explains why some demonstrations can show interesting system-level behaviour without providing every feature expected from a complete jailbreak.

IS PS5 FIRMWARE 14.10 JAILBROKEN?
Not through a verified, publicly available complete jailbreak.
Gezine's reported demonstration suggests that meaningful progress may have been achieved privately, but the underlying technique has not been publicly documented in enough detail for independent reproduction.
ZigZagBoi1's research has demonstrated native userland ROP execution, but not kernel memory read/write access.
The separate WebKit research project also remains experimental.
Therefore, PS5 owners running firmware 14.10 should not interpret these developments as confirmation that a downloadable jailbreak is available.

WHAT ABOUT FIRMWARE 14.00?
Firmware 14.00 is also important because it reportedly patched the vulnerability used by Relapse.
Some earlier hypervisor research may remain relevant to firmware 14.00, but compatibility requires a working exploit chain.
The latest firmware 14.10 demonstration does not automatically establish a public jailbreak for firmware 14.00.

WHAT ABOUT PS5 PRO?
The PS5 Pro shares important elements of the PS5 software security architecture.
However, compatibility with specific exploits depends on firmware, hardware differences and testing.
The reported firmware 14.10 demonstration does not establish that the same technique works on every PS5 Pro.

WHAT HAPPENS NEXT?
The next major milestone would be a public technical explanation or reproducible release demonstrating kernel-level access on firmware 14.10.
Researchers will also be watching for new payloads, additional firmware support, improvements in homebrew compatibility and further hypervisor research.
For now, the publicly documented ROP experiments and ongoing WebKit investigations provide useful technical evidence of progress.
Gezine's reported demonstration is a separate development whose underlying technique remains private.

WHY THIS MATTERS
The latest research demonstrates that PS5 security continues to attract serious technical investigation.
Even after Sony patches previously discovered vulnerabilities, researchers continue examining the console's operating system and security architecture.
These efforts may eventually support additional homebrew applications, system research and experimental uses of PS5 hardware.
However, there is an important difference between a private technical demonstration and a stable public jailbreak that ordinary users can install.
MicLinks Radar will continue following verified developments involving kernel exploits, hypervisor access, firmware compatibility and major homebrew releases.

CURRENT PS5 JAILBREAK STATUS — 20 OCTOBER 2026
Firmware 13.20: Public kernel and hypervisor research available through supported exploit projects.
Firmware 13.60: Public kernel and hypervisor research available through supported exploit projects.
Firmware 14.00: Earlier Relapse vulnerability reportedly patched; no new complete public jailbreak verified.
Firmware 14.10: Debug Settings access reportedly demonstrated privately by Gezine.
Firmware 14.10 userland: Native ROP execution publicly documented by ZigZagBoi1.
Firmware 14.10 WebKit: Active security research, but no complete public jailbreak chain established.
Firmware 14.10 kernel exploit: Reported private progress; no independently reproducible public release verified

The conversation

Join the discussion

Ask questions. Share ideas. Reply to other readers.

0 comments

Add your comment

Keep it respectful and lawful. No hate, scams, piracy links or instructions for unauthorised access. Read our community guidelines.

Comments appear immediately. Your name and message are public. Be respectful; names are not verified.

No comments yet. Start a useful conversation.