Switch 2 security takes a hit as hackers unlock homebrew access
A tethered software exploit gives researchers homebrew and reverse-engineering access to Nintendo's new console, but it is not a consumer-ready jailbreak.
A security researcher has demonstrated a software-only, partial jailbreak of the Nintendo Switch 2, opening a route to homebrew, reverse engineering and game modding without a hardware modification. The tethered exploit is not a turnkey consumer hack, but it shows that Nintendo's new console has a serious research target only months into its life. 1
How the Switch 2 exploit works
The exploit chain begins with the original Switch version of SmileBasic 4, a programming environment that runs on Nintendo hardware. Researcher Sammy Hajhamid, who publishes as Pepsipu, says he used a macOS or Linux computer on the same network to run a Node.js package and communicate with the console. The setup is tethered: the user needs the external computer and must repeat the process rather than simply booting into a permanent custom firmware installation. 1
Hajhamid describes using OpenAI's Codex to probe the SmileBasic 4 interpreter. A custom test harness sent USB commands to the console, displayed results over HDMI and even power-cycled the system through a Bluetooth-controlled light switch. After roughly two weeks of work, that testing uncovered a 32-bit integer overflow triggered when items are removed from an array.
That overflow exposed an array pointer, giving the researcher read and write access to parts of system memory. The next step was to examine the Switch 2's internal system modules. Hajhamid says a further buffer overflow in the console's FileSystem services module exposed a cached data pointer, leading to arbitrary read and write privileges. From there, a forged filesystem process provided a route to native code execution. 2
What the jailbreak enables
The researcher says the current userland access is enough to run homebrew, reverse-engineer software, modify Switch 2 games, back up save files and reach most of the console's peripherals through memory-mapped input and output. That is a broad list, but it should not be confused with a polished public jailbreak tool. The project remains technical, tethered and dependent on a compatible development environment.
The public proof of concept is nevertheless substantial. Hajhamid has shown modified characters running in Mario Kart World, while other researchers have demonstrated early developer tools and Vulkan-related experiments on exploited hardware. Those experiments do not automatically translate into an easy install for ordinary Switch 2 owners, but they demonstrate that the exploit reaches beyond a theoretical crash.
The project is documented in the ns2jb repository, where the researcher has published the technical work rather than presenting it as a consumer product. 2 That distinction matters: console exploits can expose personal data, break saves, trigger account penalties or leave a device unusable if copied carelessly. Nintendo's online services also give the company reasons to detect and respond to modified software.
Nintendo has not announced a response
Nintendo has not publicly acknowledged the specific exploit in the material reviewed for this report. The company has not announced a system update, a closure date for the relevant vulnerabilities or a policy change connected to the demonstration. That means the immediate impact is best understood as a warning about the platform's security surface, not as a sudden invitation for everyone to modify a Switch 2.
The timing is still significant. The Switch 2 combines a new operating environment with a large installed base and an active homebrew community inherited from the original console. Once a chain is public, security researchers, modders and Nintendo's own engineers can all study the same technical route. Patching one vulnerability may not be enough if the chain depends on several separately reachable components.
For owners, the sensible response is to keep the console updated, avoid untrusted code and treat social-media claims about effortless Switch 2 jailbreaks with suspicion. For researchers, the release offers a detailed look at how a seemingly modest interpreter bug can become a path towards privileged execution when it is combined with deeper filesystem weaknesses.
Our opinion
This is an important security story because it shows the difference between a console being difficult to modify and a console being impossible to study. Nintendo's hardware and software protections have not been magically swept aside: the exploit is tethered, technically demanding and still developing. But the chain demonstrates that SmileBasic 4 was not an isolated sandbox, and that carefully composed bugs can cross the boundary from userland experimentation to meaningful system access.
The responsible next step is disclosure and patching, not a rush to turn the proof of concept into a consumer piracy kit. Nintendo should explain what it has fixed once a patch is available, while the research community should keep separating reproducible security work from clickbait instructions that put other people's consoles and accounts at risk.