<?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-09-29T02:12:37.114539+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/cve-2026-35630</id>
    <title>CVE-2026-35630 — OpenClaw &lt; 2026.5.18 - QQBot Missing Approver Identity Enforcement in Native Approval Buttons</title>
    <updated>2026-09-29T02:12:37.153319+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw before 2026.5.18 contains an authorization bypass vulnerability in QQBot native approval buttons that fails to enforce configured approver identity. Non-approver users can click approval buttons to resolve pending exec or plugin approval requests without proper authorization.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-35630"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-mgq6-vr84-7m2j</id>
    <title>GHSA-mgq6-vr84-7m2j — OpenClaw: QQBot native approval buttons did not enforce configured approver identity</title>
    <updated>2026-09-29T02:12:37.153489+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary</p>
<p>OpenClaw's QQBot channel can deliver native approval buttons for exec and plugin approvals. In affected releases, the button callback path resolved approvals without enforcing the configured QQBot approver identity.</p>
<p>The text command approval path used the authorization check; the issue was specific to native QQBot approval buttons.</p>
<p>### Affected configurations</p>
<p>This affects deployments where QQBot native approval buttons are enabled and an approval message is visible to a QQ user who is not configured as an approver.</p>
<p>### Impact</p>
<p>A non-approver who could see the approval message could click an approval button and resolve the pending request. Depending on the pending approval, this could allow an exec or plugin action that should have required an authorized approver.</p>
<p>### Patched Versions</p>
<p>The first stable patched version is `2026.5.18`.</p>
<p>### Mitigations</p>
<p>Upgrade to `openclaw@2026.5.18` or later. Before upgrading, avoid delivering native approval buttons into QQ conversations that include users who should not be able to approve.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-mgq6-vr84-7m2j"/>
  </entry>
</feed>
