https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 18:37:07 +0000 https://vulnerability.circl.lu/vuln/cve-2026-41358 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.4.2 fails to filter Slack thread context by sender allowlist, allowing non-allowlisted messages to enter agent context. Attackers can inject unauthorized thread messages through allowlisted user replies to bypass sender access controls and manipulate model context.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.4.2 fails to filter Slack thread context by sender allowlist, allowing non-allowlisted messages to enter agent context. Attackers can inject unauthorized thread messages through allowlisted user replies to bypass sender access controls and manipulate model context.</p> https://vulnerability.circl.lu/vuln/cve-2026-41358 https://vulnerability.circl.lu/vuln/ghsa-qm77-8qjp-4vcm <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary</p> <p>Before OpenClaw 2026.4.2, Slack thread starter and thread-history context fetched through the API was not filtered by the effective sender allowlist. Messages from non-allowlisted senders could still enter the agent context when an allowlisted user replied in the same thread.</p> <p>## Impact</p> <p>A Slack deployment that relied on sender allowlists could still feed non-allowlisted thread content into the model context through thread history. This was a sender-access-control bypass on Slack thread context, not a direct channel-auth bypass.</p> <p>## Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.4.1` - Patched versions: `&gt;= 2026.4.2` - Latest published npm version: `2026.4.1`</p> <p>## Fix Commit(s)</p> <p>- `ac5bc4fb37becc64a2ec314864cca1565e921f2d` — filter Slack thread context by the effective allowlist</p> <p>## Release Process Note</p> <p>The fix is present on `main` and is staged for OpenClaw `2026.4.2`. Publish this advisory after the `2026.4.2` npm release is live.</p> <p>OpenClaw thanks @AntAISecurityLab for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary</p> <p>Before OpenClaw 2026.4.2, Slack thread starter and thread-history context fetched through the API was not filtered by the effective sender allowlist. Messages from non-allowlisted senders could still enter the agent context when an allowlisted user replied in the same thread.</p> <p>## Impact</p> <p>A Slack deployment that relied on sender allowlists could still feed non-allowlisted thread content into the model context through thread history. This was a sender-access-control bypass on Slack thread context, not a direct channel-auth bypass.</p> <p>## Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.4.1` - Patched versions: `&gt;= 2026.4.2` - Latest published npm version: `2026.4.1`</p> <p>## Fix Commit(s)</p> <p>- `ac5bc4fb37becc64a2ec314864cca1565e921f2d` — filter Slack thread context by the effective allowlist</p> <p>## Release Process Note</p> <p>The fix is present on `main` and is staged for OpenClaw `2026.4.2`. Publish this advisory after the `2026.4.2` npm release is live.</p> <p>OpenClaw thanks @AntAISecurityLab for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-qm77-8qjp-4vcm