OpenClaw EUVD-2026-26097

Exploitation requires two specific conditions: (1) the application must be restarted, which the attacker either triggers directly (if they have infrastructure access) or exploits through induced failure (denial-of-service, resource exhaustion); and (2) a Tlon configuration entry must have been previously set to an empty-array value during normal operation (the deliberate revocation action). The vulnerability does NOT require unauthenticated network access to the configuration file directly - only the ability to cause an application restart. Default OpenClaw deployments are vulnerable if they use Tlon configuration and restart frequently (e.g., containerized deployments with rolling updates or cloud-native autoscaling). Deployments that rarely restart or that do not rely on Tlon configuration have lower practical risk despite the same code flaw.

The CVSS score of 6.3 with attack vector network and low complexity indicates moderate risk, but the attack requires a persistence trigger (AT:P - attacker-triggered event) and impacts only confidentiality and integrity at low scope (confined to the affected resource). The KEV status is unknown; no EPSS score is provided. The real-world risk is nuanced: this is not an unauthenticated remote code execution, but rather a configuration persistence attack that requires (1) the ability to cause an application restart (either legitimate maintenance window or denial-of-service leading to restart) and (2) prior knowledge that specific Tlon configuration was revoked. The attack is automatable (no user interaction required once restart occurs), making it a concern for environments where application restarts are frequent or adversary-controllable. However, the limited scope (low impact to C/I, no A impact) and requirement for application restart constrain real-world exploitability compared to the CVSS base score suggests. This is a privilege-abuse or configuration-tampering risk rather than a critical remote takeover vector; prioritize based on your organization's restart frequency and whether Tlon configuration revocation is part of active security incident response.

An administrator revokes a sensitive Tlon configuration entry (such as an OAuth token or service account credential) in response to a suspected compromise, intending to immediately block that authentication path. An attacker with the ability to trigger an application restart (via induced denial-of-service, maintenance window exploitation, or cloud orchestration access) causes OpenClaw to restart. On startup, the migration logic reads the empty-array value from memory and incorrectly interprets it as a missing entry, then rehydrates the revoked configuration from the persisted file state. The attacker can now re-authenticate using the 'revoked' credential, bypassing the intended revocation control.