PS5 Relapse Exploit
AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get privacy and security gear delivered free — and shop member deals

  • Fast, free delivery on millions of items
  • Access to Prime Big Deal Days deals on October 6–7
  • Prime Video, Amazon Music and more included
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The Relapse-Exploit project on GitHub describes a browser and kernel exploit chain for PS5 systems running firmware 7.00 through 13.60. Its maintainers warn that attempts can stall the browser or cause the console to hang or panic; the source does not establish success rates or detail what access the chain enables after execution.

The Relapse-Exploit project documents a browser and kernel exploit chain for PlayStation 5 consoles running firmware 7.00 through 13.60. The GitHub page describes a network-settings configuration and a browser-based launch route, while warning that attempts may fail or cause the console to hang or panic.

According to the project’s GitHub instructions, users set the PS5’s primary DNS to 45.56.67.85 and then either run a local Python server or open the project’s hosted page in the console browser. The page says default payloads are stored in the payloads/ directory and that, after a successful run, an ELF loader listens on port 9021. These are project instructions, not independent verification that the chain works on every listed system.

The project describes the browser stage as using JavaScriptCore information leaks and a structured-clone object-pool mismatch to corrupt a typed array. It says the kernel stage combines an address leak with an aio_multi_wait use-after-free race to establish kernel read/write access. The supplied documentation does not give a success rate, explain all supported configurations, or independently demonstrate what users can do with that access.

The maintainers credit Sonic_Iso with the kernel exploit, Jordy with the WebKit exploit and kernel bug, ntfargo and ufm42 with exploit development, and Dr. Yenyen with testing. They also list contributions from TheFlow, SlidyBat, Flatz, cow, nhk, bollarz, Sleirsgoevy, EchoStretch and EarthOnion. The project says it is for educational and security research purposes and warns of instability, data loss and possible account bans.

At a glance
reportWhen: Current status: project documentation d…
The developmentThe Relapse-Exploit GitHub project has published usage notes and technical details for an exploit chain targeting PS5 firmware 7.00 through 13.60.

A Broad Firmware Support Range

The stated range, firmware 7.00 to 13.60, makes the project relevant to owners and researchers assessing console security across multiple PS5 software versions. The documented browser-to-kernel chain also illustrates how a browser vulnerability and a kernel bug can be combined to reach a higher level of system access.

For users, the project’s own warnings are material: its notes say WebKit may require repeated attempts and that the kernel stage may hang or panic the console. The documentation also flags data loss and account bans as possible risks. It does not establish how often these outcomes occur or whether particular accounts or console configurations face different risks.

Amazon

Top picks for "relapse exploit"

As an affiliate, we earn on qualifying purchases.

How Relapse Describes the Chain

The project presents two linked stages: a browser exploit followed by a kernel exploit. Its account says the browser stage corrupts a typed array after information leaks and an object-pool mismatch; the kernel stage uses an address leak and a race involving aio_multi_wait to gain kernel read/write capability.

The usage notes describe both a locally served option and a hosted page, alongside a recommended DNS address. The source advises reloading if the browser stalls and rebooting before another attempt if the kernel stage hangs or panics. No date, version-by-version test results, or independent technical assessment is included in the supplied material.

“Webkit may need several attempts, reload the page if the browser stalls.”

— Relapse-Exploit project maintainers

Success Rates and Effects Remain Unreported

The supplied project page does not report a success rate, list testing results for each firmware release, or establish whether all PS5 models and configurations within the range behave alike. It also does not explain the full practical effect of the stated kernel read/write access or provide independent confirmation of the claims.

The timing of the project’s release is not stated in the material provided, so its current maintenance status and whether the instructions reflect the latest available system software are unclear. The project warns of account bans but gives no estimate of their likelihood or detail on how that risk arises.

Further Testing Would Clarify Support

The project page is the source for its firmware range, setup instructions and stability notes. Further published test results could clarify which versions and configurations have been checked, how often the exploit chain succeeds, and what users should expect after the loader starts. No such results or future milestone are identified in the supplied material.

Anyone following the project should check its GitHub page for current documentation and treat the stated range and behavior as maintainer claims. The page advises using the software only on devices users own or are authorized to test, and in line with applicable laws.

Key Questions

Which PS5 firmware versions does Relapse say it supports?

The project lists firmware 7.00 through 13.60. The supplied source does not include independent verification or results for each version.

Does the project say every attempt will work?

No. Its notes say the browser may need several attempts and can stall. They also warn that the kernel stage may hang or panic the console.

What does the project say the exploit chain does?

The maintainers describe a browser stage that corrupts a typed array and a kernel stage that establishes kernel read/write access. The provided material does not detail the full practical effects of that access.

What risks do the maintainers list?

The project warns of system instability, data loss and account bans, and says the software is provided without warranty. It says users assume the risks of use.

Source: hn

FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Ethical Hacking Degree: Is It Necessary for a Career in Cybersecurity?

Uncover the truth about the necessity of an ethical hacking degree for cybersecurity careers and discover how it can elevate your expertise.

Ethical Hacking: Vulnerability Analysis Videos – Learn How to Detect Vulnerabilities

Dive into ethical hacking videos for vulnerability analysis to discover the secrets of detecting vulnerabilities and fortifying cybersecurity – a must-read for all!

Cloud Security Vs Ethical Hacking: the Key Differences

Leverage the distinctions between cloud security and ethical hacking to strengthen data protection and thwart cyber threats.

How To Enter And Break Out Of The Avast Antivirus Sandbox: Part 2

A Safa Team post describes exploiting an Avast driver double-fetch flaw on Windows 11 and notes a newer Windows mitigation blocks the technique.