The Switch 2 Has Been Jailbroken. Nintendo Pulled the Game, Not the Bug

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

2026-10-24 · News

Affiliate disclosure: This article contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

On 22 October 2026, the Nintendo Switch 2 was jailbroken for the first time. No soldering, no modchip, no hardware glitch. A $25 programming app from the eShop and a software bug chain were enough.

Nintendo reacted within about a day. Most people read that reaction as a patch. It was not a patch, and the distinction matters a lot if you are trying to work out whether this is still live.

Here is what actually happened, what the jailbreak can and cannot do, and why this does not turn a Switch 2 into the emulation handheld some headlines implied.

The Short Version

A software only jailbreak called ns2jb was released on 22 October 2026. It needs no hardware modification.
It runs on firmware 23.0.1, which is the current Switch 2 system version, released on 1 October 2026.
It starts from SmileBASIC 4, a roughly $25 Switch 1 programming app that still runs on the Switch 2.
An AI coding agent did a large share of the work. OpenAI's Codex was pointed at the problem with an unattended hardware rig built to reboot the consoles after every crash.
It is tethered and userland only. It dies on reboot. There is no kernel exploit and no custom firmware.
Nintendo delisted SmileBASIC 4 rather than shipping a firmware fix. As of 24 October 2026, no system update addresses the underlying bugs.
Homebrew is already running. A homebrew launcher, Doom, Super Mario Bros and modded characters in Mario Kart World have all been demonstrated.
It does not make the Switch 2 a retro handheld. Nothing here resembles what Switch 1 custom firmware eventually became.

What ns2jb Actually Is

The release is credited to security researcher Sammy Hajhamid, who published it under his own name and has been named across mainstream coverage of the story.

The chain starts in SmileBASIC 4. That is a real commercial product, a BASIC programming environment sold on the eShop for about $25. It is a Switch 1 app, but it runs on the Switch 2 through backwards compatibility, which is the part Nintendo presumably did not weigh heavily.

Inside SmileBASIC 4 there is a 32 bit integer overflow. That gets code running inside the app's own sandbox, which on its own is not very interesting. The second step is what matters. A buffer overflow in the console's filesystem service carries the exploit out of the app and into a system process, which is where the useful access lives.

The result is native code execution on a retail Switch 2, on the newest firmware, with no hardware work at all.

The AI Part Is Not Marketing

This is the detail that made the story travel, and unusually, it holds up.

OpenAI's Codex was used heavily to find and build the chain. The interesting engineering is the rig around it. A Switch 1 and a Switch 2 were wired up through two JetKVM devices, which give remote keyboard, video and mouse access to a physical machine. Then a Bluetooth light switch was added to physically press the console's power button whenever it crashed.

That combination is what made the AI useful. Hunting a memory bug means crashing the target over and over, and a console that needs a human to pick it up and reboot it caps you at whatever pace a person can sit there. Remove the human from the reboot and an agent can keep grinding unattended.

Reported turnaround on the working chain was about two weeks.

We have covered AI showing up in emulation and homebrew work repeatedly this year, and most of it has been either undisclosed or overstated. This one is disclosed, specific, and the methodology is the actual news.

What It Can Do

Access demonstrated or stated so far:

Homebrew. A homebrew launcher, reported as HBLauncher v1.0.0, was shown running on 23 October 2026. Doom and Super Mario Bros were the first homebrew titles demonstrated on it.
Game modding. The announcement demo put Hatsune Miku, Peter Griffin, Cinnamoroll and other unofficial characters into Mario Kart World.
Save file backups. Pulling your own save data off the console.
Filesystem access. This is the one with consequences, and it is why Switch 2 game data has already started being extracted. We cover that separately in Switch 2 games are being dumped.
Hardware access. Reading and writing console peripherals directly through memory mapped IO.
Graphics. There is video suggesting Vulkan rendering works, which would matter for anything graphical that people want to port.

What It Cannot Do

This is the half that most headlines skipped, and it is most of the story.

It is tethered. The jailbreak does not survive a power cycle. Shut the console down and you are back to a stock Switch 2, and you have to run the whole thing again. There is no persistence.

It is userland, not kernel. Code execution inside a system process is not control of the system. There is no kernel exploit yet.

There is no custom firmware. Nothing like Atmosphere exists for the Switch 2, and a tethered userland hole is not the foundation one normally gets built on. That is the gap between "homebrew runs" and "the console is yours."

It does not enable piracy by itself. It gives filesystem access, which is a step toward extracting data. It does not install or run copied games.

Nintendo Pulled the Game, Not the Bug

This is the part worth being precise about, because the common version of this story is wrong.

Nintendo did not ship a firmware patch. Within roughly a day of the release, SmileBASIC 4 was delisted from the eShop. It disappeared from North American and European listings first, then from the rest, with Japan reported last and some alternative storefront links reportedly still resolving for a while afterward. Nintendo has not publicly confirmed why, and has not acknowledged the jailbreak at all.

So what Nintendo removed was the entry point for new users, not the vulnerability.

Three things follow from that.

Copies already installed keep working. Delisting a title from a storefront does not reach into consoles and delete it. If the app is on the console, the door is still there.
The underlying bugs are unpatched. Firmware 23.0.1 shipped on 1 October 2026, three weeks before any of this, and its release notes cover one thing: software occasionally taking a long time to start, pause or close. No security fix. The filesystem bug is still open as of 24 October 2026.
A real patch is the obvious next move. Nintendo can close the filesystem overflow in a system update whenever it chooses, and historically does. Delisting is the fast lever, not the fix.

Nintendo has run this exact play before. The 3DS era had its own homebrew entry points removed from sale rather than patched first.

A Warning We Will Repeat

If you are thinking about trying this, two things are genuinely risky and neither is hypothetical.

Console bans. Nintendo can detect modified consoles over an online connection and has banned aggressively for far less. Going online after running an exploit, or updating firmware afterward, is how people lose access to their own account and digital library.

Your library is at stake, not just the hardware. Everything you bought digitally lives behind the account that gets banned.

We are reporting this because it is the biggest Switch 2 story of the year. We are not providing instructions, and we do not link to the code.

Does This Change Anything for Handhelds?

Short answer: no, and the reason is worth understanding.

The reason people care about Switch 1 custom firmware is that it eventually turned the console into one of the best emulation handhelds ever made. Persistent custom firmware, a homebrew ecosystem, RetroArch, standalone emulator ports, and a huge screen with real controls. That took years of work on top of a full kernel compromise.

The Switch 2 is nowhere near that. You have a tethered userland hole that resets every time the console sleeps. Running Doom as a proof of concept is the very first rung of that ladder, not a sign the rest is close.

And on the actual emulation question, nothing has moved. No commercial Switch 2 game runs under any public emulator, on any hardware, PCs included. The jailbreak does not change that, because the hard part of Switch 2 emulation was never getting files off the console. Our Switch 2 emulation status page covers where those projects really stand.

If what you want is a device that plays your retro library today, that is still a dedicated handheld, and the market for those is in a good place right now.

Check Retroid Pocket 5 Price on Amazon

Check Anbernic RG40XXV Price on Amazon

What to Watch Next

Four specific things, in rough order of how much they would matter.

A kernel exploit. This is the one that changes the trajectory. Userland access is a curiosity. Kernel access is how custom firmware becomes possible.
A firmware update with a security fix. The filesystem bug is the valuable half of the chain, and patching it closes the route even for people who already own SmileBASIC 4.
A second entry point. Delisting one app only works until someone finds a bug in something that cannot be delisted, like a system app or a first party game.
Whether SmileBASIC 4 returns. If it comes back after a firmware update, that tells you Nintendo considers the chain dead.

Frequently Asked Questions

Has the Switch 2 jailbreak been patched?

Not as of 24 October 2026. Nintendo delisted SmileBASIC 4 from the eShop, which stops new people from buying the app the exploit starts in, but that is a storefront change rather than a software fix. The underlying filesystem bug is still unpatched, and firmware 23.0.1 from 1 October 2026 contains no security fix. Copies of the app already installed on a console still work.

Can I jailbreak my Switch 2 right now?

Only if SmileBASIC 4 is already installed on it, since the app has been delisted and cannot be bought any more. Even then you should weigh the ban risk, because Nintendo can detect modified consoles online and a ban takes your whole digital library with it. We do not publish instructions or links for this.

Does the Switch 2 jailbreak let you pirate games?

Not by itself. It gives filesystem access, which people are using to extract game data, but it does not install or run copied games. There is also no Switch 2 emulator that could play extracted games on anything else.

What firmware does ns2jb work on?

Firmware 23.0.1, which is the current Switch 2 system version. That is unusual. Console exploits normally arrive against firmware that is already a few versions behind.

Is the Switch 2 jailbreak permanent?

No. It is tethered, which means it has to be run again every time the console is powered off. There is no custom firmware and nothing persists across a reboot.

Did AI really jailbreak the Switch 2?

An AI coding agent did a substantial share of the work, and the researcher has said so openly. The part that made it work was the test rig: two consoles wired up for remote access, plus a Bluetooth switch to physically press the power button after each crash, so the agent could keep crashing and rebooting the hardware without a person present. A human designed that setup and directed the work.

Can I use this to emulate Switch 2 games on a handheld?

No. No commercial Switch 2 game runs under any public emulator on any hardware, and neither of the two serious Switch 2 emulator projects has an Android build. Getting files off a console was never the bottleneck.

Will Nintendo ban me for this?

It is a real possibility. Nintendo detects console modification through online connections and has a long record of banning for it. The ban applies to the account and the console, so your purchased digital games go with it.

Written 24 October 2026. This is a fast moving story and the firmware situation is the detail most likely to change. If Nintendo ships a system update with a security fix, the answer to "does this still work" changes with it.