Disclosed weakness · no CVE recorded

OpenClaw for iOS could retain gateway credentials in device backups

OpenClaw · OpenClaw for iOS · Gateway settings

First documented disclosure · Review checkpoint

Summary

A setup code entered in Gateway settings could remain in plaintext app preferences after a failed or abandoned setup and be included in a device backup.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The maintainer records a correction. The reviewed sources identify no malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The settings field persisted user input as a preference. Setup codes can include a bootstrap token, an access token or a password.

Conditions required

A user enters a credential-bearing code in the affected settings field. Disclosure to another party requires access to the preferences or a backup containing them.

Potential impact

A backup or device-data reader could obtain a still-valid gateway credential, with access depending on its permissions and validity.

Affected versions and configurations

The maintainer confirmed the behavior on iOS 2026.11.3 and the development build. The earliest affected version is unspecified.

Fix and mitigation status

The correction is listed in stable release 2026.11.4 and was also documented in prerelease 2026.11.5-beta.3. This verifies inclusion in the source release. App Store distribution was not established.

Practical next steps

Install an iOS build containing the correction and launch it to clear the legacy preference. Rotate a still-valid credential if an affected backup was accessible to others.

Operating lesson

Keep temporary pairing input in memory and include device backups when assessing exposure from older builds.

Evidence and limits

The fix keeps newly entered codes in memory and removes the old preference on launch. The source confirms cleanup on upgrade from 2026.11.3.

Sources