CVE-2026-100543 in OpenClaw
Summary
by MITRE • 09/26/2026
OpenClaw (npm package openclaw) before 2026.8.1 could include deterministic hashes computed over the original, unredacted configuration in redacted configuration responses. When the Gateway password had low entropy and the remaining configuration values were reconstructable, these hashes acted as offline password verifiers: a caller able to obtain the redacted configuration (for example via config.get) could test password candidates offline without going through the rate-limited Gateway authentication path. Recovering the password could grant the documented shared-secret operator authority. Secret references were not affected in the same way. The issue is fixed in 2026.8.1.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 09/26/2026
The vulnerability identified within OpenClaw versions prior to release 2026.8.1 represents a critical flaw in how configuration data and authentication credentials are handled during redaction processes. Specifically, the software failed to properly obscure deterministic cryptographic hashes associated with user passwords when generating redacted configuration responses. In normal operation, systems often return sanitized or partially obscured configurations for debugging or administrative purposes while keeping sensitive secrets hidden. However, this implementation error allowed these unredacted password hashes to persist in the output returned by functions such as config.get. This oversight effectively bypassed the intended security controls designed to protect credential material from exposure through configuration retrieval mechanisms.
From a technical perspective, the core issue lies in the failure to apply consistent redaction logic across all components of the configuration object. While secret references were correctly excluded or masked, the deterministic hashes computed over the original unredacted configuration remained visible. These hashes are typically used for efficient password verification during authentication flows. By exposing them externally, the system inadvertently provided attackers with a static target for cryptographic analysis. This transforms what should be an online, rate-limited authentication process into an offline attack vector where adversaries can perform rapid hash cracking without triggering security alerts or account lockout mechanisms associated with failed login attempts.
The operational impact of this vulnerability is severe, particularly in environments where the Gateway password exhibits low entropy. If a user selects a weak or common password, the exposed deterministic hashes act as effective offline verifiers. An attacker who gains access to these redacted configuration responses can utilize standard brute-force or dictionary attack tools against the hash values locally on their own hardware. This eliminates network-based rate limiting and allows for significantly faster credential recovery compared to interacting with the live authentication service directly. Once the password is recovered, the attacker obtains operator authority based on the shared-secret model used by OpenClaw, granting them full administrative control over the system.
This flaw aligns closely with CWE-209, which describes the generation of an error message that includes sensitive information making it useful to attackers, and CWE-538, regarding the inclusion of file or directory paths in data sent out for detection by external actors when such exposure leads to security impacts. Furthermore, from a threat modeling perspective using the MITRE ATT&CK framework, this vulnerability facilitates Credential Access techniques specifically T1078, Valid Accounts, as it allows an attacker to obtain legitimate credentials through information disclosure rather than exploitation of authentication logic flaws directly. It also relates to T1529, System Shutdown or Reboot implications if combined with other privileges, but primarily serves as a direct path for unauthorized access via credential harvesting.
Mitigation strategies must prioritize immediate upgrading to version 2026.8.1 where this redaction defect has been resolved. In addition to patching the software, administrators should enforce strong password policies that ensure high entropy in all Gateway passwords, thereby increasing the computational cost required to crack any potential hashes even if they were exposed. It is also advisable to review access controls around configuration retrieval endpoints to ensure that only authorized personnel with appropriate privileges can request detailed system configurations. Regular audits of redaction logic across all API responses and data serialization processes should be conducted to prevent similar oversights in future updates or related modules within the OpenClaw ecosystem.