As reported by The Hacker News, a researcher operating under the handle forcequit has published an iOS sandbox escape dubbed worse_query that allows a malicious application to read the data containers of other apps on iOS 26 and iOS 27 — without a jailbreak or kernel exploit. Apple's November 9 updates (iOS 27.2.1 and iOS 26.7.3) do not address the issue, and no CVE has been assigned at the time of writing.
Why This Matters
The iOS sandbox is the foundational security boundary that isolates one application's data from another. If a logic flaw can circumvent it at the application layer — without requiring kernel-level privilege escalation — then every piece of unencrypted data stored by any app becomes potentially accessible to a malicious counterpart. This is particularly devastating for cryptocurrency wallet apps, which may store seed phrases, private keys, or cached credentials within their sandboxed containers.
The critical distinction here is that worse_query operates through App Group containers — a mechanism Apple provides for apps from the same developer to share data. The proof-of-concept demonstrates that this sharing mechanism can be abused to reach beyond the intended scope, accessing containers belonging to entirely unrelated applications. This is a design-level concern, not a simple memory corruption bug, which explains why a rapid patch may be difficult to deliver.
Threat Model and Exposure Scope
While no active exploitation has been confirmed, the practical risk is asymmetric. The attack requires a victim to install a malicious app that leverages the worse_query technique. Sideloaded apps — installed via tools like AltStore or SideStore, which are increasingly common in EU markets due to Digital Markets Act compliance requirements — represent the most likely delivery vector. The WQ Files file manager app, built atop worse_query by developer Christoph Kolbicz, demonstrates that functional tooling already exists and is publicly available.
What remains unconfirmed is whether a malicious app distributed through the official App Store could exploit this technique. If so, the exposure surface expands dramatically to include any iOS user who installs a seemingly benign application.
Vulnerability Summary
| Attribute | Detail |
|---|---|
| Name | worse_query (iOS sandbox escape via App Group abuse) |
| CVE | Not assigned as of November 10, 2026 |
| Affected OS | iOS 26 and iOS 27 (tested through 27.2.1) |
| Severity | High (unpatched, credential/key exposure) |
| Patch Status | Not available — iOS 27.2.1 and 26.7.3 do not list a fix |
| Active Exploitation | None confirmed publicly |
| Requires Jailbreak | No |
| Delivery Vector | Malicious sideloaded app; App Store feasibility unconfirmed |
Who Is Most at Risk
Broader Implications
This vulnerability arrives at an uncomfortable intersection for Apple. The company faces regulatory pressure to open its ecosystem while simultaneously defending a sandbox model that now has a publicly documented logic-level bypass. The App Group container mechanism appears to be the root of the problem — it was designed for legitimate inter-app data sharing but its scope enforcement is evidently insufficient. Any fix will likely require tightening App Group entitlement validation at the OS level, which could break legitimate apps that depend on cross-app data sharing.
For the cryptocurrency ecosystem, this underscores a persistent lesson: hot wallets on mobile devices remain a fragile security perimeter. A sandbox escape of this nature means that even well-coded wallet applications cannot guarantee the confidentiality of their stored secrets if the underlying OS isolation fails.
Shield53 Recommendations
Immediate Actions
- Remove all sideloaded apps from any iOS device used for cryptocurrency or sensitive credentials. Audit installed apps via Settings → General → VPN & Device Management for unfamiliar enterprise certificates or profiles.
- Update to iOS 27.2.1 or iOS 26.7.3 immediately — while it does not fix worse_query, it patches iMessage and Bluetooth vulnerabilities that could serve as initial access vectors in a combined attack chain.
- Migrate crypto assets to a hardware wallet or a fresh wallet created on a known-clean device. Treat any device that has run sideloaded apps as potentially compromised.
- Reset all active sessions on crypto exchange accounts and wallet services to invalidate any potentially stolen session tokens.
- Enable hardware-backed key isolation where wallet apps support Secure Enclave storage — though note this may not fully protect against an attacker who can read the app container directly.
Detection Considerations
- For enterprise MDM administrators: deploy restrictions on App Group entitlements for managed devices and monitor for sideloaded app installation via device compliance policies.
- For wallet app developers: encrypt all sensitive material at rest using a key derived from the Secure Enclave, and avoid storing plaintext seed phrases in standard app container files.
- Monitor for the presence of WQ Files or similar file manager apps on managed devices.
Strategic Guidance
Until Apple confirms a patch, organizations should assume that iOS app-level sandbox isolation is not a reliable control for protecting high-value secrets. Layer your defenses: use hardware wallets for cryptocurrency, enforce MDM app allowlisting on corporate devices, and treat any sideloaded application as a potential sandbox escape vector. This is not a temporary advisory — it is a window of exposure with no announced end date.
