Switch 2 jailbreak: Codex cracked Nintendo's console in 2 weeks

Short answer: Yes, the Switch 2 is jailbroken. ns2jb, published October 18 2026 by Sammy Hajhamid (@pepsipu), runs native code on firmware 23.0.1, the latest, with no modchip. It took about 2 weeks of work with OpenAI's Codex agents doing the bug hunting, 500 days after launch, and Nintendo's whole security stack (PAC, CFI, execute-only memory) got walked around through a BASIC programming game.

TL;DR: We pulled all 114 public Switch and Switch 2 flaws on switchbrew and 12 of them were disclosed in 2026, the most since 2022. Half of all 114 (55) sit in system modules, the exact layer ns2jb broke through the fs filesystem service. Nintendo has sold 23.68 million Switch 2 consoles, and the bug that opened them was a 0x301-byte buffer and a path with a backslash in it.

Key numbers

What	Number	Source, checked Oct 26 2026
Hands-on time to the jailbreak	about 2 weeks	pepsipu.com
Days from Switch 2 launch (June 5 2025) to ns2jb	500	Wikipedia, pepsipu.com
Days from launch to first public Switch 2 flaw (ldnhax)	159	switchbrew
Public Switch / Switch 2 flaws on record	114	switchbrew
Flaws disclosed in 2026 so far	12	switchbrew
Share of flaws in system modules	55 of 114 (48%)	switchbrew
Switch 2 consoles sold	23.68 million	Nintendo IR, as of June 30 2026
ns2jb repo, 5 days after going up	100 stars, 43 forks	GitLab API

The most locked-down Nintendo ever fell to a BASIC interpreter

Nintendo built the Switch 2 like a vault. Pointer authentication (PAC, signed pointers so you cannot forge a jump), control-flow integrity (CFI, the CPU checks where calls land) and execute-only memory (XOM, you cannot even read the code you want to hijack).

Hajhamid's own write-up says the WebKit browser route, where everyone looks first, hit exactly that wall. So the agents went around it.

The way in was SmileBASIC 4, a Switch 1 game that still runs on the Switch 2. A 32-bit integer overflow in its REMOVE command turned a string array into an out-of-bounds read and write. Switch 1 games have no PAC, so the fancy mitigations simply were not in the room.

That is the whole story of console security in one bug: you are only as strong as the oldest thing you still let run. Backward compatibility is a feature Nintendo sells, and it is also the door.

Codex did the grinding, a human picked the targets

Let's kill the hype and the cope at the same time. Hajhamid says the "make no mistakes" prompt in his photo was a joke, and that a /goal for userland execution on its own did not succeed. The jailbreak took real effort for about 2 weeks.

But look at what the agents actually did. Codex found the SmileBASIC overflow. Codex found the BufferedStorage cache object to overflow into for arbitrary read/write. Several Codex instances ran in parallel on different sysmodules, mostly audio and ldn, while the human chose fs because Switch 1 code showed it serves decrypted code.

The rig is the tell: JetKVMs feeding controller input and HDMI video to the agents, plus a cheap Bluetooth light-switch flicker from Amazon that physically presses the power button when the console crashes. That is an autonomous fuzzing lab on a desk. The Mario Kart World mod at the end was, in his words, entirely vibecoded in a day.

So the "AI can't do real security work" crowd is cooked. And the "AI did it alone" crowd is wrong too. The real headline is scarier for Nintendo: one skilled person plus a few agents now runs like a small exploit team.

12 flaws in 10 months: the pace is picking up

We pulled every row of switchbrew's public flaw tables (the CSV is below). 2017 had 14 disclosures, 2018 had 17, 2022 had 22. Then three quiet years of 7 or 8.

2026 already has 12, and the year is not done. Five audio bugs landed on a single day, September 14 2026, all patched in 23.0.0. A DHCP server overflow in lp2p got a CVE on October 15. Even Mario Kart World and Splatoon 3 made the list.

Our read: the quiet years were Switch 1 being "done", and 2026 is the Switch 2 scramble with agents in the loop. We cannot prove how many of those 12 had AI help. But the audio cluster lines up with exactly where Hajhamid's Codex instances chose to dig, and nobody should bet on the curve going down from here.

Follow the money: who wins, who loses

Nintendo loses the most. 23.68 million Switch 2 owners are on firmware 23.0.1 or older, and the fs bug is a software bug. Nintendo can patch it, but it cannot pull SmileBASIC off every console that already has it, and Hajhamid notes the WebKit browser is reachable offline. Expect a firmware update and, if history is a guide, lawyers.

Nintendo's bug bounty loses the argument. Hajhamid writes that the bounty has "probably incentivized many" to go after WebKit. The bounty pointed researchers at the browser; the hole was in the filesystem service. Paying people to look under the streetlight is a choice.

Homebrew, modders and preservationists win. Save backups off the console, reverse engineering, game mods, and a path toward custom firmware. The repo hit 100 stars and 43 forks on GitLab within 5 days.

OpenAI wins the free ad of the year. "Codex modded Mario Kart World" is a better launch video than anything their marketing team cut this quarter. Nintendo just became the demo.

Why this is bigger than one console

The trick that sealed it is a lesson for every signed-code system. The loader checks Nintendo's signature on the program metadata and the developer's signature on the header hash. Looks airtight.

But it trusts fs to serve files that match that hash. Own fs, and you swap the executable after the signatures pass. Every check was correct; the trust between the checkers was the bug.

If you ship anything with a "verify then load" pipeline (app updates, plugin systems, model weights), this is your threat model now: agents are cheap, patient and great at finding the one service everyone else trusts. Read our breakdowns of the iPhone zero-day pace and container escapes in runc and youki for the same pattern elsewhere, and keep up with it on the news desk, games and AI agents.

What this means for you

If you own a Switch 2 and want homebrew, do not update past 23.0.1 until the scene says it is safe; if you play online and want no trouble, update the moment Nintendo ships a fix. If you build software, assume an attacker with agents will test every internal service boundary this month, not this year: find the component everything trusts and fuzz it yourself first.

Stuck on a Rust or AI API bug your own agents cannot crack? Our paid fix gets it fixed within 24 hours or you get a full refund.

Sources

• Sammy Hajhamid, Jailbreaking the Switch 2, October 18 2026
• ns2jb repository on GitLab, checked October 26 2026
• Switchbrew, Switch System Flaws, pulled October 26 2026
• Nintendo IR, Dedicated Video Game Sales Units, as of June 30 2026
• Wikipedia, Nintendo Switch 2, checked October 26 2026
• smilehax, the original 3DS SmileBASIC exploit
• Hacker News discussion, 835 points, October 2026