CVE-2026-95815 in OpenClaw
Summary
by MITRE • 09/22/2026
OpenClaw iOS before 2026.8.11 logs complete agent deep-link URLs including persistent bearer keys to unified logs as public diagnostic data. Attackers who obtain diagnostic archives can recover unrotated keys and replay them in forged deep links to submit agent requests without local confirmation prompts.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 09/22/2026
The vulnerability identified involves a critical flaw in the logging mechanism of OpenClaw iOS versions prior to 2026.8.11, where sensitive authentication credentials are inadvertently exposed through system diagnostic logs. Specifically, when agents utilize deep-link URLs for navigation or command execution within the application, these full Uniform Resource Locators are recorded in the unified log subsystem as part of standard diagnostic data collection. This logging behavior fails to sanitize or mask persistent bearer keys embedded within the query parameters of these URLs, resulting in the plaintext storage of high-value authentication tokens on the device's file system and accessible via standard iOS diagnostic tools.
From a technical perspective, this issue represents a classic case of sensitive information exposure through improper data handling during routine operational processes. The deep-link mechanism is designed to facilitate seamless user interaction by passing parameters directly within the URL structure rather than using more secure methods like POST bodies or local storage with encryption. However, the iOS unified logging system captures these URLs for troubleshooting purposes without applying necessary redaction filters for authentication headers or query string tokens. Consequently, any process or application with access to device logs can retrieve these entries, effectively bypassing the intended security controls that rely on the secrecy of bearer keys.
The operational impact of this vulnerability is severe due to the potential for credential replay attacks. An attacker who gains physical access to a locked device through exploitation of other vulnerabilities, or who compromises an account with sufficient privileges to export diagnostic archives from iCloud backups or local exports, can extract these unrotated bearer keys. Once obtained, these keys allow the attacker to forge deep-link URLs that authenticate as legitimate agents without triggering local confirmation prompts such as Face ID, Touch ID, or passcode entry. This effectively neutralizes multi-factor authentication mechanisms and allows for unauthorized command execution, data exfiltration, or manipulation of agent behavior within the OpenClaw ecosystem.
This flaw aligns with CWE-532, which covers information exposure through log files, where sensitive data is written to logs that may be accessible to unauthorized parties. Furthermore, it relates to CWE-798, involving the use of hardcoded credentials, as the persistent nature of these keys suggests they are not being rotated frequently enough or are treated with insufficient confidentiality during transmission and logging processes. In terms of adversary tactics, this vulnerability facilitates techniques associated with ATT&CK T1530, which involves data from cloud storage objects, if backups containing logs are accessed remotely, or more directly supports credential access through local log extraction methods often seen in post-exploitation phases where attackers seek to maintain persistence and escalate privileges.
Mitigation strategies must prioritize immediate remediation by upgrading OpenClaw iOS to version 2026.8.11 or later, which presumably implements proper sanitization of diagnostic logs to exclude sensitive query parameters. In the interim, administrators should enforce strict access controls on device diagnostics and encourage users to rotate any potentially exposed bearer keys immediately if they suspect their devices have been compromised or accessed by unauthorized entities. Additionally, future development cycles should incorporate secure logging practices that automatically mask authentication tokens using standardized frameworks such as those defined in OWASP guidelines for mobile application security, ensuring that diagnostic data remains useful for troubleshooting without compromising the confidentiality of critical credentials.