So, we currently have a userspace exploit using the web browser that gives us basic code execution. This currently works on versions 4.0.0 to 5.1.0. It has access to read and write memory, the basic library functions, and that's about it. We can't access the filesystem or likewise install or change anything on it(not that we'd want to since we still have no idea how it works). You can find the exploit here. Frequently Asked Questions Q: Why can't we access the filesystem/*insert limitation here*? A: Since this is only a userspace exploit and we don't yet have access to the kernel, we only have access to what permissions the app, in this case the web browser, has. Since the browser has no need for accessing the filesystem or any external storage, we don't have access to that. Q: Is it safe to update to 5.0.0/5.1.0? A: YES! I can finally say that yes, it is once again safe to update to the latest version (5.1.0). Thanks to Marionumber1 and chadderz, the ROP chain was ported and reworked to work on 5.0.0/5.1.0. Q: What's the latest version that this exploit currently exists in? A: This currently works on any version from 4.0.0, up to the current version, which as of posting this, is 5.1.0. Q: I won't want to miss out on homebrew, how can I update to 4.1.0? A: Mario Kart 8 comes with 4.1.0 on the disc, so go buy it (because it's not like it's a bad game), keep your system offline, and then update with the disc. Q: I want to update to 5.0.0/5.1.0 but I don't want to have my system update on me. What do I do?? A: There are two different things you can do. One solution is to turn off Standby Mode, which as of 5.0.0 allows your Wii U to install updates while you're sleeping. Go into Settings and go to Power Settings, and then just turn off "Standby Functions". This does disable Quick Boot though. Another solution would be to block the following URL with your router: nus.cdn.wup.shop.nintendo.net Q: So now that we have access to executing code on the system, what's next? A: Well, now we need to start tearing apart the kernel and IOSU, because we'll need both a kernel exploit and IOSU access to be able to dump the rest of the keys (including the common key which will allow us to simply download binaries off of NUS (Nintendo Update Service) and decrypt them for easy use). Then it's on to finding a possible way to install and run content off the system menu (since the Wii U checks signatures at load time as well as install time). Then we have to rework the SDK to allow for distribution for basic homebrew, and then it's all uphill from there. Q: What does this mean for the average user? Can we expect real homebrew in the near future? A: For the average person, this does nothing of significance other then it allows us access to basic functions that will allow us to see how the system works. We still need to find a kernel exploit and an IOSU exploit which will allow us full access to the system, and then we need to understand how the system works before we do anything significant.