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:53 +0000 https://vulnerability.circl.lu/vuln/cve-2026-53856 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw 2026.4.23 before 2026.4.24 contains an insecure file permissions vulnerability in config recovery that restores OpenClaw.json with overly broad permissions. Local attackers on shared hosts can read sensitive configuration data by exploiting the recovery path to access the restored config file.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw 2026.4.23 before 2026.4.24 contains an insecure file permissions vulnerability in config recovery that restores OpenClaw.json with overly broad permissions. Local attackers on shared hosts can read sensitive configuration data by exploiting the recovery path to access the restored config file.</p> https://vulnerability.circl.lu/vuln/cve-2026-53856 https://vulnerability.circl.lu/vuln/ghsa-rwp6-7w3q-75fq <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>Config recovery could restore openclaw.json with broad file permissions. In affected versions, a local recovery path after configuration repair could leave the restored config file more readable than intended.</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 expose local configuration to other same-host users where OS permissions allow it. 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.24`.</p> <p>### Mitigations</p> <p>check `openclaw.json` permissions after recovery on shared hosts 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>Config recovery could restore openclaw.json with broad file permissions. In affected versions, a local recovery path after configuration repair could leave the restored config file more readable than intended.</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 expose local configuration to other same-host users where OS permissions allow it. 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.24`.</p> <p>### Mitigations</p> <p>check `openclaw.json` permissions after recovery on shared hosts 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-rwp6-7w3q-75fq