OpenClaw iOS EUVD-2026-87470

Exploitation requires local access to the credential store: specifically an unencrypted iOS device backup or an extracted App Group container from the device running OpenClaw for iOS before 2026.8.11. Because credentials are written as cleartext JSON to App Group UserDefaults instead of the iOS Keychain, no cryptographic barrier protects them once the file is obtained. Limiting factors: this is not remotely reachable (AV:L); iOS encrypts backups and applies Data Protection to Keychain items by default, so the attacker must defeat or bypass backup encryption, have physical/forensic access, or run on a jailbroken/compromised device to reach the App Group container. PR:L reflects that some level of local/device access is needed rather than pure remote anonymous access.

This is a genuine but low-urgency data-protection weakness, not an internet-facing critical. The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N, 6.8 Medium) correctly models a LOCAL attack that discloses confidentiality only - no direct integrity or availability impact on the vulnerable system itself. There is no EPSS score, no CISA KEV listing, and no public exploit code identified, so exploitation is neither confirmed nor probabilistically flagged as widespread. The real risk hinges on a precondition the attacker must already satisfy: possession of an unencrypted iOS device backup or an extracted App Group container. Given that iOS enforces backup encryption and Data Protection by default, and that App Group containers are not casually accessible on a non-jailbroken device, the practical attack surface is narrow. The elevated consequence is that the recovered Gateway tokens/passwords grant operator authority to the OpenClaw Gateway - a real privilege - but that authentication step happens off the vulnerable iOS app and is a downstream/subsequent impact, which is why VC:H but VI:N/VA:N and SC/SI/SA:N is defensible. Net: a legitimate CWE-312 credential-storage hygiene bug that matters most in device-loss/forensic-access threat models, not a remotely exploitable priority.

An attacker obtains an unencrypted iTunes/Finder backup of an iPhone running OpenClaw, or extracts the App Group container from a lost, seized, or malware-compromised device, and reads the cleartext JSON in UserDefaults to recover the Gateway token and password. They then use those credentials to authenticate to the OpenClaw Gateway with full operator authority from their own machine. No public exploit code is required - recovery is a simple file/plist read once backup or container access is achieved.