Nintendo Patched the Switch 2 Jailbreak. It Never Admitted It Existed

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-11-10 · 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.

In October we wrote that Nintendo had pulled the game, not the bug. The Switch 2 had been jailbroken, and the company's answer was to quietly delist the $25 app the exploit started in.

On 9 November 2026 it pulled the bug.

Firmware 23.5.0 closes the vulnerability that made the jailbreak work. Nintendo's patch notes do not mention it. They talk about accessibility settings and a gifting feature. The security fix is in there, it is just not written down anywhere, and the only reason anybody knows is that people went looking.

Here is what actually changed, what survived, and why a game publisher recalled a boxed game nine days before this update made the recall pointless.

The Short Version

Firmware 23.5.0 shipped on 9 November 2026. Some regions saw it land in the early hours of 10 November.
It patches the operating system bug behind the jailbreak. Dumping and modding Switch 2 games is closed again on current firmware.
Nintendo's patch notes say nothing about it. Officially this update is about accessibility options and eShop gifting.
Only half the chain died. The entry points still work. What is gone is the escape out of the game and into the system.
A second entry point had appeared on 1 November, through a Civilization VII cartridge. The publisher reportedly pulled the physical version. Then this update made that moot.
It still works on consoles that never took the update. That is a small and shrinking group, because the console updates itself whenever it is online.
Nothing here walks back Switch 2 emulation or the native port route. Those consume data that was already extracted.
Nintendo has still never acknowledged any of this, including that the jailbreak exists.

What Nintendo Says 23.5.0 Does

The official notes are short and ordinary.

You can configure accessibility settings during first time setup now. There is groundwork for an upcoming feature that lets you gift eShop products to someone in your Nintendo Account family group, which goes live after eShop maintenance on 17 November 2026. A few more text to speech and GameChat languages were added. You can save notes about people on your friend list. An error that hit some Switch to Switch 2 system transfers was fixed.

Then the line that does all the heavy lifting: "General adjustments and fixes were made to improve the user experience."

That is the whole disclosure. There is no security section, no CVE, no mention of anything being closed.

Two details worth noting. This is a joint update, so the original Switch went to 23.5.0 on the same day. And Nintendo skipped four version numbers to get here. The previous release was 23.0.1 on 1 October 2026, and there was no 23.1, 23.2, 23.3 or 23.4 in between.

What It Actually Does

The clearest account came from a well known Switch dataminer who went through the update, not from Nintendo. Their summary:

"The OS exploit used in the recent jailbreak has been patched in version 23.5.0. Dumping and modding games will be impossible again from this point forward, with the exception of some cartridge games (and maybe game updates) that are released in the near future."

To understand what that means you need the shape of the original exploit, which we laid out when it landed.

The jailbreak was two bugs stacked on top of each other. The first was a 32 bit integer overflow inside SmileBASIC 4, a programming app sold on the eShop. That gets code running, but only inside the app's own sandbox, which is close to useless on its own. The second was a buffer overflow in the console's filesystem service, and that is the one that carried the exploit out of the game and into a system process. Everything people cared about lived in step two. Reading game files, extracting data, modding, all of it.

Nintendo patched step two. Step one is untouched.

So the entry points still work. You can still get code running inside SmileBASIC 4, and inside the other game that was found later. What you cannot do any more is leave. In the dataminer's words, homebrew is now locked to whatever the game can already do, which is not much.

That distinction is the whole story. The console is not more secure against people getting code to run. It is secure again against that code going anywhere useful.

The Second Door Opened, Then Closed Too

When we covered the jailbreak we listed four things to watch for. One of them was a second entry point, on the logic that delisting one app only works until somebody finds a bug in something Nintendo cannot pull.

That happened on 1 November 2026, and it is a better story than the one we predicted.

A tool called CivSwitch gets code running on a Switch 2 through Civilization VII. Specifically the Switch 1 edition, playing on a Switch 2 through backwards compatibility, which is the same backwards compatibility path the first jailbreak used. The bug is in the game's multiplayer chat box. Text typed into it was being handled as JavaScript and run, which is the kind of flaw you normally meet in a badly built website rather than a strategy game.

Three things made it awkward for Nintendo in a way a delisting could not fix.

It needed the physical cartridge. Version 1.0.0 of the Switch 1 card, specifically. The code in a box digital edition does not work, because the version you download is not the version pressed onto the cart.

You cannot delist a cartridge that has already been sold. Every copy on a shelf or in somebody's drawer was a working entry point.

It was not really a jailbreak. It gave userland code execution through the same shape of hole, and it covered Switch 1 and Switch 2 firmware from 20.x.x up to 23.0.1. Getting the code in required a Raspberry Pi Pico flashed to pretend to be a USB keyboard, which typed the payload into the chat box for you.

Then the part that is genuinely unusual. 2K reportedly withdrew the physical cartridge from sale. The evidence for this is a retailer order cancellation in Germany, with a message saying the publisher had withdrawn the physical version of the game over technical and security related requirements, and retailers being told to offer the code in a box version instead or refund the order. That is a retailer explaining itself to a customer. It is not a statement from 2K, and 2K has not publicly confirmed a recall, so treat it as reported rather than settled.

And nine days later, firmware 23.5.0 made all of it irrelevant.

Because the Civilization VII bug was only ever step one. It got code running inside the game. It still needed the same operating system hole to go anywhere, and that hole is now closed. Both doors lead to the same locked corridor.

That is the honest lesson of this whole episode. Pulling SmileBASIC 4 off the eShop did nothing to the vulnerability. A publisher pulling boxed copies of a strategy game off shelves did nothing to the vulnerability. The only thing that ever closed it was a system update, and when Nintendo finally shipped one it closed every entry point at once, including ones nobody has found yet.

Who This Still Works For

Almost nobody, and the reason is boring rather than technical.

The console updates itself. A Switch 2 checks for system software and installs it whenever it is online, and that is the default behaviour. Anyone who wanted to stay on 23.0.1 needed to have turned automatic updates off before today, and needed to not care about anything that forces an update.

Online services require current firmware. Online play and the eShop both expect you to be up to date. Holding on an old version means giving those up, and giving up the account features attached to them.

So in practice the surviving population is people who deliberately parked a console offline on 23.0.1, which is a hobbyist decision made in advance, not something you can choose now.

There is one caveat in the dataminer's note worth repeating, which is the exception for "some cartridge games (and maybe game updates) that are released in the near future." The plain reading is that a console held back on old firmware can still receive new game data physically, because a cartridge does not force you to take a system update the way an eShop download effectively does. So a holdout console is not frozen in October, it can still take in some games released after today. We are reading that caveat rather than quoting a mechanism, because the exact behaviour has not been spelled out anywhere.

The ban warning from October has not changed and is worth repeating. Nintendo detects modified consoles over an online connection and bans for it, and the ban reaches the account as well as the hardware. Your purchased digital library goes with it.

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

What This Does Not Undo

This is the part most coverage is getting slightly wrong, so it is worth being precise.

Data that was already extracted still exists. A firmware patch closes a route. It does not reach backwards and unmake files that came out before it shipped. Everything pulled off a console between 22 October and 9 November is still out there.

Switch 2 emulation is unaffected. The two forks that publish working builds, Eglantine and Lichii, read game data that has already been dumped. They never needed a live jailbreak on your console, and they do not need one now. Where that actually stands is in our Switch 2 emulation status page and the Lichii piece.

The native port route is unaffected too. The toolchain that rebuilds Switch 2 games into Mac and iPhone apps works on already extracted data. The one wrinkle we flagged, that Switch 2 data comes off a jailbroken console already decrypted so no key file is needed, is still true of the data. It just has a much narrower supply line now. See Switch games running natively on Apple and Android.

What the patch really does is narrow the pipeline, not close the destinations. Fewer new games get captured from here, and the ones that do come from a shrinking set of offline consoles.

The place that stings most is preservation, and we flagged why in our piece on Switch 2 dumping. Many Switch 2 cartridges are Game Key Cards that contain no game data at all, just a key that triggers a download. There is nothing on the card to dump. Pulling the installed copy out of console storage was the only way those titles were ever going to be captured, and that route just got a lot narrower.

Does This Change Anything for Handhelds?

No, and the answer is the same one we have given every time this story has moved.

No Switch 2 game runs on a Retroid, an AYN or an Anbernic. Not because those devices are too slow, but because nothing targets them. Neither emulator fork produces an Android build, and the one ARM Linux build that exists was tested on a real handheld and black screens. The native port route needs Apple silicon.

The jailbreak never changed that, and the patch does not change it back.

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 good shape right now.

Check Retroid Pocket 5 Price on Amazon

Check Anbernic RG40XXV Price on Amazon

What to Watch Next

Our October list had four items. Two of them just fired. Here is the updated version.

A kernel exploit. Still the only thing that changes the trajectory. Everything so far has been userland, which is why a single system update could close it. Kernel access is what custom firmware gets built on, and nothing public is close.
An entry point in something Nintendo cannot remove. A system app, a first party game, a built in feature. Delisting and recalling both worked as stalling tactics precisely because the holes were in optional products.
Whether either game comes back. If SmileBASIC 4 returns to the eShop, or Civilization VII cartridges go back on sale, that is Nintendo and 2K telling you they consider the chain dead.
Whether anything is found in 23.5.0 itself. The jailbreak originally landed against the newest firmware available, which is unusual and suggests the people looking are not working from a backlog of old bugs.

Frequently Asked Questions

Has the Switch 2 jailbreak been patched?

Yes. Firmware 23.5.0, released on 9 November 2026, closes the operating system bug the jailbreak relied on. This is a real software fix, unlike Nintendo's first response in October, which was to delist the app the exploit started in. Nintendo's published patch notes do not mention the security fix at all.

Does the Switch 2 jailbreak still work on old firmware?

On a console that never installed 23.5.0, yes. In practice that is a very small group, because a Switch 2 installs system updates automatically whenever it is online, and online play and the eShop both require current firmware. Anyone still on 23.0.1 had to have turned automatic updates off beforehand.

What does firmware 23.5.0 officially change?

Accessibility settings can now be configured during first time setup, there is groundwork for an eShop gifting feature that goes live after maintenance on 17 November 2026, a few more text to speech and GameChat languages were added, you can save notes about friends, and a Switch to Switch 2 transfer error was fixed. The security fix is not listed. It falls under "general adjustments and fixes."

Can you still dump or mod Switch 2 games?

Not on current firmware. The entry points still get code running inside the game they start in, but the escape into the system is gone, so homebrew is limited to whatever that game could already do. Data extracted before 9 November 2026 still exists and is unaffected.

What is CivSwitch?

A tool released on 1 November 2026 that got code running on a Switch 2 through the Switch 1 edition of Civilization VII, using a flaw in the game's multiplayer chat that ran text typed into it as JavaScript. It needed version 1.0.0 of the physical cartridge and a Raspberry Pi Pico programmed to act as a USB keyboard. It gave userland code execution rather than a full jailbreak, and firmware 23.5.0 closed the system level hole it depended on.

Did 2K really recall Civilization VII cartridges?

It is reported but not confirmed by the publisher. Buyers in Germany received retailer cancellation messages saying the publisher had withdrawn the physical version of the game over technical and security related requirements, with code in a box versions or refunds offered instead. 2K has not publicly confirmed a recall. Either way, firmware 23.5.0 closed the vulnerability the cartridge was being used to reach.

Does this patch stop Switch 2 emulation?

No. The two forks that publish downloadable builds, Eglantine and Lichii, read game data that has already been extracted. They never needed a live jailbreak on your console. The same is true of the native port toolchain that rebuilds Switch 2 games into Mac and iPhone apps. The patch narrows the supply of newly extracted games rather than breaking the tools that use them.

Should I update my Switch 2 to 23.5.0?

For almost everyone, yes, and the console will do it on its own anyway. Declining it means losing online play and eShop access, which is only a trade worth making if you had already set a console aside specifically to keep an old firmware. Running an exploit and then going online is how people get their account and their digital library banned.

Will there be another Switch 2 jailbreak?

Probably, eventually. Both known entry points were found in ordinary consumer software, and the first one landed against the newest firmware available rather than an old version, which suggests active research rather than a backlog of old bugs. What matters is whether anyone finds a kernel level hole, because everything public so far has been userland, which is why one system update could close all of it at once.

Written 10 November 2026. Nintendo has still not acknowledged the jailbreak, the patch, or anything in between. If that changes, or if the chain turns out to survive somewhere we did not expect, we will update this page rather than quietly rewrite it.