https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 17:52:59 +0000 https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-53855 <p><strong>Affected:</strong> Homebrew: openclaw-cli</p> <p>### Summary</p> <p>Shell positional parameters could weaken strict inline-eval checks. In affected versions, a command request that combines allowlisted tools with shell positional arguments could place inline-eval content in a shell carrier not covered by the strict check.</p> <p>This advisory is scoped to the named feature and configuration. It does not change OpenClaw&#39;s trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.</p> <p>### Impact</p> <p>When the affected feature is enabled and reachable, this could run shell-provided content outside the intended allowlist rule. Practical impact depends on the operator&#39;s configuration and whether lower-trust input can reach that path.</p> <p>### Patched Versions</p> <p>The first stable patched version is `2026.4.2`.</p> <p>### Mitigations</p> <p>avoid allowlisting shell carrier patterns and require approval for shell wrappers until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.</p> <p><strong>Affected:</strong> Homebrew: openclaw-cli</p> <p>### Summary</p> <p>Shell positional parameters could weaken strict inline-eval checks. In affected versions, a command request that combines allowlisted tools with shell positional arguments could place inline-eval content in a shell carrier not covered by the strict check.</p> <p>This advisory is scoped to the named feature and configuration. It does not change OpenClaw&#39;s trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.</p> <p>### Impact</p> <p>When the affected feature is enabled and reachable, this could run shell-provided content outside the intended allowlist rule. Practical impact depends on the operator&#39;s configuration and whether lower-trust input can reach that path.</p> <p>### Patched Versions</p> <p>The first stable patched version is `2026.4.2`.</p> <p>### Mitigations</p> <p>avoid allowlisting shell carrier patterns and require approval for shell wrappers until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.</p> https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-53855 https://db.gcve.eu/vuln/cve-2026-53855 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.4.2 contains an inline-eval bypass vulnerability allowing authenticated operators to weaken strict allowlist checks via shell positional parameters. Attackers can combine allowlisted tools with shell positional arguments to place inline-eval content in shell carriers outside intended allowlist rules, enabling execution of unapproved shell-provided content.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.4.2 contains an inline-eval bypass vulnerability allowing authenticated operators to weaken strict allowlist checks via shell positional parameters. Attackers can combine allowlisted tools with shell positional arguments to place inline-eval content in shell carriers outside intended allowlist rules, enabling execution of unapproved shell-provided content.</p> https://db.gcve.eu/vuln/cve-2026-53855