CVE-2026-112251 in clawhost
Summary
by MITRE • 10/19/2026
A vulnerability was detected in antoinersx clawhost up to 0.0.45. This affects the function handleRequest of the file apps/clawhostgo/src/main/services/reverseProxy.ts of the component Reverse Proxy. Performing a manipulation of the argument token results in open redirect. The attack can be initiated remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/19/2026
The vulnerability identified within antoinersx clawhost versions up to 0.0.45 represents a critical security flaw located specifically within the reverse proxy component of the application architecture. This issue resides in the handleRequest function found in the source file apps/clawhostgo/src/main/services/reverseProxy.ts. The core technical deficiency is an open redirect vulnerability, which occurs when the software fails to properly validate or sanitize user-supplied input before using it as a destination for redirection operations. Specifically, manipulation of the token argument allows an attacker to control where the application redirects users after authentication or other proxy-related processes are completed. This type of flaw is classically categorized under CWE-601, which defines URL Redirection to Untrusted Site, and often intersects with CWE-20 regarding improper input validation. The lack of strict allow-listing for redirect targets means that any arbitrary Uniform Resource Locator can be injected into the token parameter, leading to unintended navigation behavior.
From an operational perspective, this vulnerability poses significant risks beyond simple misdirection. Open redirects are frequently leveraged as a vector for phishing attacks where attackers craft malicious links that appear legitimate because they originate from the trusted domain of clawhost. When users click these links, they are redirected to a fraudulent site designed to steal credentials or distribute malware, thereby eroding trust in the platform and potentially compromising user data integrity. Furthermore, this flaw can be exploited to bypass access controls if certain security mechanisms rely on redirect URLs for state validation or callback verification processes. The ability to manipulate the token argument remotely means that no prior authentication is required to initiate the attack, significantly lowering the barrier to entry for malicious actors. This aligns with several techniques observed in the MITRE ATT&CK framework, particularly those related to social engineering and credential harvesting via deceptive redirection tactics.
The exploit code for this vulnerability has already been made public, which drastically increases the likelihood of active exploitation in the wild. Publicly available exploits allow less sophisticated threat actors to leverage known weaknesses without needing to develop custom payloads from scratch. This situation is compounded by the vendor's lack of response despite being contacted early regarding the disclosure. The absence of a patch or official mitigation strategy leaves users exposed indefinitely unless they implement their own defensive measures. In such scenarios, it is imperative for system administrators and developers to review the reverse proxy configuration immediately. Potential mitigations include implementing strict allow-lists for redirect destinations rather than relying on blacklist approaches, which are inherently prone to bypasses through encoding variations or protocol ambiguities. Additionally, enforcing Content Security Policy headers that restrict navigation targets can provide a layer of defense-in-depth against open redirects even if the underlying application code remains unpatched until an official update is released by the vendor.