bad_query README

The project's README from github.com/forcequitOS/bad_query. As one markdown file: README.md.

bad_query

A sandbox escape for iOS 26.0 - 26.6.1 / 27.0b4.

This is a proof-of-concept for developers and not anything meaningfully usable at the moment.

bad_query can access the following paths:

/var/containers/Data/System (iOS 27)
/var/containers/Shared/SystemGroup/* (iOS 27)
/var/mobile/Containers/Data/Application/*
/var/mobile/Containers/Data/InternalDaemon/*
/var/mobile/Containers/Data/PluginKitPlugin/*
/var/mobile/Containers/Shared/AppGroup/* (Requires App Group sacrifice on iOS 26)
/var/mobile/Containers/Shared/AppGroup (iOS 27)

This might also work on iOS 18 but I haven't tested literally at all so ymmv

bad_query (forcequitOS/bad_query)

Searching Database…

What is this?badquery is a proof-of-concept sandbox escape for iOS 26 and 27, written in C — code that demonstrates breaking out of the iOS app sandbox.
Is this a jailbreak I can install on my iPhone?No — the author is explicit that it is just a proof-of-concept for developers and not anything meaningfully usable at the moment. Think demonstration, not tool.
How do I build and run it?No build or run steps are documented: the repo is plain C with no Makefile, scripts, or dependency manifest, so reproducing it means reading and compiling the sources yourself.
Which iOS versions does it cover?iOS 26.0 through 26.6.1, plus the 27.0 beta 4. The author adds that iOS 18 might work too, but he has not tested that at all — your mileage may vary.
What can badquery actually reach once it escapes the sandbox?Filesystem paths outside the app sandbox: the README names the specific paths badquery can access, which is the concrete payoff of the escape.
Can I reuse the code in my own project?Probably not without permission — the repo ships no license, so the code stays under the author's exclusive copyright by default. Reading and learning from it is fine.
Size
<0.1 MB
Stars
276
Updated
CommitAug 11
Age
2mo
Commits · 90 Days