A public proof-of-concept with no confirmed patch

Binance has issued a warning to its users about a publicly released iOS sandbox escape that could allow a malicious app to read files belonging to other apps on the device. According to The Hacker News, the technique — published on GitHub under the name worse_query — affects iPhones running iOS 26 and iOS 27. Apple's updates for both versions, shipped the day before the warning, do not list a fix for the issue.

For crypto users, the stakes are unusually high. A sandbox escape that grants one app read access to another app's container undermines the core security boundary that protects sensitive data on iOS. On a crypto wallet, that container may hold seed phrases, private keys, signing material, and cached authentication tokens.

What the researcher published

The escape was released on a Sunday by a researcher who goes by the handle forcequit. The name worse_query suggests the technique builds on query-based interaction between apps — the mechanism iOS uses to let apps ask the system about other installed apps, URLs, and related state — and abuses it to reach further than intended.

Binance's warning frames the exposure in concrete terms: seed phrases, private keys, and login credentials could all be exposed to a malicious application that leverages the escape. The company has not confirmed that an exploit has been observed in the wild, and the disclosure appears to be researcher-driven rather than the result of an active attack campaign.

Why a sandbox escape matters more than a typical iOS bug

iOS security rests on two pillars: code signing and app sandboxing. Each app runs in its own container with limited access to shared system resources, and Apple's review process is meant to ensure that apps do not attempt to break out of that container. A working sandbox escape weakens the second pillar directly.

The practical consequence is that the trust model between apps collapses. A user who installs a seemingly harmless utility — a flashlight app, a photo filter, a QR scanner — could inadvertently hand an attacker a foothold from which to read wallet data stored by a separate, legitimate app. Users cannot easily audit an app's behaviour before installing it, and App Store review does not guarantee that a novel escape technique will be caught.

This is not the first time iOS sandboxing has been challenged, but the combination of a public proof-of-concept, a claimed broad version range (iOS 26 and 27), and a lack of a documented fix in the latest updates is what makes this disclosure notable.

Apple's silence and the patch gap

The most pressing question is whether Apple has already addressed the issue silently. Apple frequently ships security fixes without public acknowledgement, and the absence of a listed fix in release notes is not proof that the vulnerability remains exploitable. However, Binance's warning explicitly notes that the updates do not list a fix, and no vendor confirmation has been published.

Until Apple responds, defenders are left with mitigation rather than remediation. That is an uncomfortable position for anyone holding significant crypto assets on a phone.

Practical guidance for wallet holders

Binance's warning points toward a defensive posture that reduces the attack surface rather than eliminating the vulnerability:

  • Treat app installation as a security decision. Every new app is a potential container neighbour. Keep the number of installed apps low, and prefer well-established developers with transparent security practices.
  • Move high-value keys off the hot device. Hardware wallets and air-gapped signing keep seed material away from any iOS container entirely, which neutralises this class of escape.
  • Watch for unusual permission prompts and unexpected behaviour from recently installed apps, particularly anything requesting broad access to files, photos, or system information.
  • Monitor vendor advisories. If Apple ships an out-of-band update or publishes a security note referencing sandbox isolation, apply it promptly.
  • Consider separate devices. Using a dedicated phone for wallets, with a minimal app footprint, limits the pool of apps that could reach wallet data.

The bigger picture: mobile wallets as a target class

Crypto wallets have become one of the most attractive targets on mobile because a single successful read of a seed phrase converts directly into irreversible financial loss. Attackers do not need remote code execution or a zero-click chain; they need one malicious app and one escape primitive.

Public proof-of-concept releases accelerate that risk. Once code is on GitHub, it is available to anyone — including operators who are willing to wrap it in a polished-looking app and push it through distribution channels. The window between disclosure and weaponisation can be short.

Binance's decision to warn users publicly, rather than wait for vendor confirmation, reflects a reasonable calculation: the downside of users being uninformed outweighs the risk of drawing attention to the technique. Whether Apple responds with a patch, a clarification, or a silent fix, the episode is a reminder that mobile sandboxing is a boundary under constant pressure — and that the safest place for a seed phrase is still a device that never touches the internet.

Users should watch for further updates from Apple and from Binance, and should not assume that installing the latest iOS release resolves this specific issue until a fix is confirmed.