<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Config-Mutation — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/config-mutation/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 05 May 2026 18:44:31 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/config-mutation/feed.xml" rel="self" type="application/rss+xml"/><item><title>OpenClaw Gateway Configuration Mutation Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-openclaw-config-mutation/</link><pubDate>Tue, 05 May 2026 18:44:31 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-openclaw-config-mutation/</guid><description>A vulnerability in OpenClaw versions before 2026.4.23 allows a compromised model with access to the `gateway` tool to persist unsafe config changes that cross security boundaries due to an insufficient denylist.</description><content:encoded><![CDATA[<p>OpenClaw versions prior to 2026.4.23 contain a vulnerability where a compromised model, granted access to the owner-only <code>gateway</code> tool, can exploit an insufficient denylist used to protect configuration settings. This denylist, intended as a model-to-operator trust boundary, failed to keep pace with the evolving config schema. This allowed sensitive subtrees to be writable through model-driven gateway config mutations. The vulnerability was addressed in version 2026.4.23 by replacing the denylist with a more secure fail-closed allowlist, restricting agent-driven configuration changes. The vulnerable entry point is owner-only, emphasizing the importance of securing the model/agent interface, which should not be considered a trusted principal.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to a model with access to the <code>gateway</code> tool, potentially through prompt injection or other compromise techniques.</li>
<li>The attacker crafts a malicious configuration payload designed to exploit the incomplete denylist.</li>
<li>The attacker uses the <code>gateway config.apply</code> or <code>gateway config.patch</code> command to submit the crafted configuration.</li>
<li>The compromised model interacts with the <code>gateway</code> tool to apply the malicious configuration changes, bypassing the insufficient denylist.</li>
<li>The malicious configuration changes are written to the OpenClaw configuration files.</li>
<li>The configuration changes persist even after OpenClaw restarts.</li>
<li>These persisted changes allow the attacker to manipulate command execution, network behavior, credential forwarding, telemetry or hook endpoints, memory/indexing surfaces, and operator policy controls.</li>
<li>The attacker achieves persistent control over OpenClaw&rsquo;s behavior, potentially leading to data exfiltration, service disruption, or privilege escalation.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows attackers to persist unsafe configuration changes within OpenClaw. These changes can affect critical system functions, including command execution, network/proxy/TLS behavior, credential forwarding, telemetry or hook endpoints, memory/indexing surfaces, and operator policy controls. The changes survive restarts, granting the attacker persistent control. While the specific number of affected installations is unknown, any OpenClaw instance running a version prior to 2026.4.23 is vulnerable.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenClaw to version 2026.4.23 or later to incorporate the fix that replaces the denylist with a fail-closed allowlist.</li>
<li>Implement strict input validation and sanitization for any data passed to the <code>gateway</code> tool to prevent prompt injection attacks, addressing the vulnerability described in the overview.</li>
<li>Monitor the execution of <code>gateway config.apply</code> and <code>gateway config.patch</code> commands for unexpected arguments or payloads that may indicate exploitation attempts, creating a detection opportunity based on observed command execution.</li>
<li>Enable file integrity monitoring on OpenClaw configuration files to detect unauthorized modifications, providing an alert mechanism if malicious changes persist on disk.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>config-mutation</category><category>vulnerability</category></item></channel></rss>