<?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>Allowlist-Bypass — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/allowlist-bypass/</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, 28 Apr 2026 19:37:42 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/allowlist-bypass/feed.xml" rel="self" type="application/rss+xml"/><item><title>OpenClaw Exec Allowlist Bypass Vulnerability (CVE-2026-41390)</title><link>https://feed.craftedsignal.io/briefs/2026-04-openclaw-allowlist-bypass/</link><pubDate>Tue, 28 Apr 2026 19:37:42 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-openclaw-allowlist-bypass/</guid><description>OpenClaw before version 2026.3.28 contains an exec allowlist bypass vulnerability (CVE-2026-41390) that allows attackers to persist trust for wrapper binaries like /usr/bin/script to execute different underlying programs, potentially leading to privilege escalation.</description><content:encoded><![CDATA[<p>OpenClaw, a security application, is vulnerable to an allowlist bypass (CVE-2026-41390) affecting versions prior to 2026.3.28. The core issue lies in how OpenClaw handles &ldquo;allow-always&rdquo; persistence, specifically when dealing with wrapper binaries like <code>/usr/bin/script</code>. The application fails to properly unwrap or inspect the underlying commands executed by these wrappers before storing trust decisions. This oversight allows an attacker to gain user approval for a benign, wrapped command. Once approved, the trust is incorrectly associated with the wrapper binary itself, enabling the execution of arbitrary, potentially malicious, commands through the same wrapper. This vulnerability can lead to privilege escalation or other unauthorized activities, as the attacker can bypass intended security restrictions by leveraging the improperly granted trust.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a vulnerable OpenClaw installation running a version prior to 2026.3.28.</li>
<li>Attacker crafts a seemingly benign command using a wrapper binary like <code>/usr/bin/script</code>, such as <code>script -q /tmp/output bash -c &quot;id&quot;</code>.</li>
<li>The user is prompted by OpenClaw to approve the execution of <code>/usr/bin/script</code>.</li>
<li>The user, believing the command is safe, approves the execution and adds <code>/usr/bin/script</code> to the &ldquo;allow-always&rdquo; list.</li>
<li>OpenClaw incorrectly persists trust for <code>/usr/bin/script</code> without unwrapping the command.</li>
<li>Attacker then executes a malicious command using the same wrapper, e.g., <code>script -q /tmp/output bash -c &quot;rm -rf /&quot;</code>.</li>
<li>OpenClaw allows the execution of the malicious command because <code>/usr/bin/script</code> is already trusted.</li>
<li>The malicious command executes, resulting in data loss or system compromise.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows attackers to bypass the intended access controls enforced by OpenClaw. An attacker can leverage a trusted wrapper binary to execute arbitrary commands, potentially leading to privilege escalation and full system compromise. The impact can range from data theft and system corruption to complete control over the affected system. This vulnerability affects any system running a vulnerable version of OpenClaw.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenClaw to version 2026.3.28 or later to patch the vulnerability described in CVE-2026-41390.</li>
<li>Implement process monitoring to detect the execution of <code>/usr/bin/script</code> or similar wrappers with potentially malicious commands as a defense in depth. Use the &ldquo;Detect Suspicious Script Wrapper Execution&rdquo; Sigma rule provided below.</li>
<li>Review existing &ldquo;allow-always&rdquo; rules in OpenClaw and remove any entries for wrapper binaries like <code>/usr/bin/script</code> that might have been added inadvertently.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>allowlist bypass</category><category>privilege escalation</category><category>cve-2026-41390</category></item><item><title>OpenClaw Microsoft Teams Plugin Sender Allowlist Bypass (CVE-2026-34506)</title><link>https://feed.craftedsignal.io/briefs/2026-03-openclaw-allowlist-bypass/</link><pubDate>Tue, 31 Mar 2026 12:16:30 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-openclaw-allowlist-bypass/</guid><description>OpenClaw before 2026.3.8 contains a sender allowlist bypass vulnerability in its Microsoft Teams plugin, allowing unauthorized senders to bypass intended authorization checks due to improper handling of empty groupAllowFrom parameters, potentially leading to information disclosure.</description><content:encoded>&lt;p>OpenClaw, a Microsoft Teams plugin, is vulnerable to a sender allowlist bypass (CVE-2026-34506) in versions prior to 2026.3.8. The vulnerability stems from a misconfiguration issue where an empty &lt;code>groupAllowFrom&lt;/code> parameter in the team/channel route allowlist leads to the synthesis of wildcard sender authorization. This allows any sender within the matched team/channel to trigger replies in allowlisted Teams routes, effectively bypassing intended authorization checks. This vulnerability was…&lt;/p>
</content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>cve-2026-34506</category><category>openclaw</category><category>microsoft teams</category><category>allowlist bypass</category></item><item><title>OpenClaw Exec Allowlist Bypass via POSIX Path Overmatching (CVE-2026-32973)</title><link>https://feed.craftedsignal.io/briefs/2026-03-openclaw-bypass/</link><pubDate>Sun, 29 Mar 2026 13:17:01 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-openclaw-bypass/</guid><description>OpenClaw before 2026.3.11 contains an exec allowlist bypass vulnerability (CVE-2026-32973) due to improper normalization of patterns, allowing attackers to execute unintended commands via wildcard matching in POSIX paths.</description><content:encoded><![CDATA[<p>OpenClaw versions prior to 2026.3.11 are susceptible to an exec allowlist bypass vulnerability, identified as CVE-2026-32973. The vulnerability stems from the <code>matchesExecAllowlistPattern</code> function&rsquo;s flawed normalization process, specifically its handling of lowercasing and glob matching. This leads to overmatching on POSIX paths, enabling attackers to circumvent intended restrictions. By leveraging the &lsquo;?&rsquo; wildcard, attackers can match across path segments to execute commands or access paths…</p>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>cve-2026-32973</category><category>openclaw</category><category>allowlist-bypass</category></item></channel></rss>