<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T23:41:55.915579+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-32914</id>
    <title>BREW-openclaw-cli-CVE-2026-32914 — OpenClaw: Command-authorized non-owners could reach owner-only `/config` and `/debug` surfaces</title>
    <updated>2026-10-08T23:41:58.458233+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary</p>
<p>OpenClaw documented `/config` and `/debug` as owner-only commands, but the command handlers checked only whether the sender was command-authorized. A lower-trust sender who was intentionally allowed to run commands could still reach privileged configuration and debugging surfaces.</p>
<p>### Impact</p>
<p>This allowed a non-owner sender to read or change privileged configuration that should have remained restricted to owners.</p>
<p>### Affected versions</p>
<p>`openclaw` `&lt;= 2026.3.11`</p>
<p>### Patch</p>
<p>Fixed in `openclaw` `2026.3.12`. Owner checks are now enforced for privileged command surfaces, and regression tests cover `/config` and `/debug` access control.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-32914"/>
  </entry>
</feed>
