<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T14:51:40.460622+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-26317</id>
    <title>BREW-openclaw-cli-CVE-2026-26317 — OpenClaw affected by cross-site request forgery (CSRF) through loopback browser mutation endpoints</title>
    <updated>2026-10-08T14:51:40.465373+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Summary
Browser-facing localhost mutation routes accepted cross-origin browser requests without explicit Origin/Referer validation. Loopback binding reduces remote exposure but does not prevent browser-initiated requests from malicious origins.</p>
<p>## Impact
A malicious website can trigger unauthorized state changes against a victim's local OpenClaw browser control plane (for example opening tabs, starting/stopping the browser, mutating storage/cookies) if the browser control service is reachable on loopback in the victim's browser context.</p>
<p>## Affected Packages / Versions
- openclaw (npm): &lt;= 2026.2.13
- clawdbot (npm): &lt;= 2026.1.24-3</p>
<p>## Details
The browser control servers bind to loopback but exposed mutating HTTP endpoints without a CSRF-style guard. Browsers may send cross-origin requests to loopback addresses; without explicit validation, state-changing operations could be triggered from a non-loopback Origin/Referer.</p>
<p>## Fix
Mutating HTTP methods (POST/PUT/PATCH/DELETE) are rejected when the request indicates a non-loopback Origin/Referer (or `Sec-Fetch-Site: cross-site`).</p>
<p>## Fix Commit(s)
- openclaw/openclaw: b566b09f81e2b704bf9398d8d97d5f7a90aa94c3</p>
<p>## Workarounds / Mitigations
- Enable browser control auth (token/password) and avoid running with auth disabled.
- Upgrade to a release that includes the fix.</p>
<p>## Credits
- Reporter: @vincentkoc</p>
<p>## Release Process Note
`patched_versions` is set to the planned next release version. Once that npm release is published, t…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-26317"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-13426</id>
    <title>cnvd-2026-13426</title>
    <updated>2026-10-08T14:51:40.465449+00:00</updated>
    <content>cnvd-2026-13426</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-13426"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-268954</id>
    <title>EUVD-2026-268954</title>
    <updated>2026-10-08T14:51:40.465467+00:00</updated>
    <content>EUVD-2026-268954</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-268954"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-26317</id>
    <title>fkie_cve-2026-26317</title>
    <updated>2026-10-08T14:51:40.465479+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw is a personal AI assistant. Prior to 2026.2.14, browser-facing localhost mutation routes accepted cross-origin browser requests without explicit Origin/Referer validation. Loopback binding reduces remote exposure but does not prevent browser-initiated requests from malicious origins. A malicious website can trigger unauthorized state changes against a victim's local OpenClaw browser control plane (for example opening tabs, starting/stopping the browser, mutating storage/cookies) if the browser control service is reachable on loopback in the victim's browser context. Starting in version 2026.2.14, mutating HTTP methods (POST/PUT/PATCH/DELETE) are rejected when the request indicates a non-loopback Origin/Referer (or `Sec-Fetch-Site: cross-site`). Other mitigations include enabling browser control auth (token/password) and avoid running with auth disabled.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-26317"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3fqr-4cg8-h96q</id>
    <title>GHSA-3fqr-4cg8-h96q — OpenClaw affected by cross-site request forgery (CSRF) through loopback browser mutation endpoints</title>
    <updated>2026-10-08T14:51:40.465505+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw, npm: clawdbot</p>
<p>## Summary
Browser-facing localhost mutation routes accepted cross-origin browser requests without explicit Origin/Referer validation. Loopback binding reduces remote exposure but does not prevent browser-initiated requests from malicious origins.</p>
<p>## Impact
A malicious website can trigger unauthorized state changes against a victim's local OpenClaw browser control plane (for example opening tabs, starting/stopping the browser, mutating storage/cookies) if the browser control service is reachable on loopback in the victim's browser context.</p>
<p>## Affected Packages / Versions
- openclaw (npm): &lt;= 2026.2.13
- clawdbot (npm): &lt;= 2026.1.24-3</p>
<p>## Details
The browser control servers bind to loopback but exposed mutating HTTP endpoints without a CSRF-style guard. Browsers may send cross-origin requests to loopback addresses; without explicit validation, state-changing operations could be triggered from a non-loopback Origin/Referer.</p>
<p>## Fix
Mutating HTTP methods (POST/PUT/PATCH/DELETE) are rejected when the request indicates a non-loopback Origin/Referer (or `Sec-Fetch-Site: cross-site`).</p>
<p>## Fix Commit(s)
- openclaw/openclaw: b566b09f81e2b704bf9398d8d97d5f7a90aa94c3</p>
<p>## Workarounds / Mitigations
- Enable browser control auth (token/password) and avoid running with auth disabled.
- Upgrade to a release that includes the fix.</p>
<p>## Credits
- Reporter: @vincentkoc</p>
<p>## Release Process Note
`patched_versions` is set to the planned next release version. Once that npm release is published, t…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3fqr-4cg8-h96q"/>
  </entry>
</feed>
