https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 23:21:52 +0000 https://vulnerability.circl.lu/vuln/cve-2026-53838 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.5.27 contains a state mutation vulnerability in node pairing reconnection that allows paired nodes to confuse approval scope decisions. Attackers can exploit reconnection logic to restore or present broader node authority than intended, potentially bypassing approval restrictions.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.5.27 contains a state mutation vulnerability in node pairing reconnection that allows paired nodes to confuse approval scope decisions. Attackers can exploit reconnection logic to restore or present broader node authority than intended, potentially bypassing approval restrictions.</p> https://vulnerability.circl.lu/vuln/cve-2026-53838 https://vulnerability.circl.lu/vuln/ghsa-83w9-h5wv-j9xm <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>Node pairing reconnection could confuse approval scope state. In affected versions, a paired or reconnecting node session could mutate pairing state in a way that changed the approval scope decision.</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 restore or present broader node authority than the operator intended. 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.5.27`.</p> <p>### Mitigations</p> <p>revoke unexpected node pairings and re-pair only trusted nodes 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> npm: openclaw</p> <p>### Summary</p> <p>Node pairing reconnection could confuse approval scope state. In affected versions, a paired or reconnecting node session could mutate pairing state in a way that changed the approval scope decision.</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 restore or present broader node authority than the operator intended. 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.5.27`.</p> <p>### Mitigations</p> <p>revoke unexpected node pairings and re-pair only trusted nodes 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://vulnerability.circl.lu/vuln/ghsa-83w9-h5wv-j9xm