<?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-25T12:33:12.631110+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-ghsa-j26j-7qc4-3mrf</id>
    <title>BREW-openclaw-cli-GHSA-j26j-7qc4-3mrf — OpenClaw: MS Teams fileConsent/invoke missing conversation binding allowed cross-conversation pending-upload consumption</title>
    <updated>2026-10-25T12:33:12.632166+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary
In `openclaw` MS Teams file-consent flow, pending uploads were authorized by `uploadId` alone. `fileConsent/invoke` did not verify the invoke conversation against the conversation that created the pending upload.</p>
<p>### Impact
An attacker who obtained a valid `uploadId` within TTL could trigger cross-conversation upload completion (accept path) or cancel a victim pending upload (decline path).</p>
<p>### Technical Details
- Pending uploads stored `conversationId`, but invoke handling consumed by `uploadId` only.
- The invoke path did not enforce conversation binding before `uploadToConsentUrl(...)` and pending-upload removal.
- Fix binds accept/decline handling to normalized conversation id match before consuming pending upload state.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published npm version (as of February 26, 2026): `2026.2.24`
- Vulnerable range: `&lt;= 2026.2.24`
- Patched in release: `2026.2.25`</p>
<p>### Remediation
Upgrade to `openclaw` `2026.2.25` (or later) once published.</p>
<p>### Fix Commit(s)
- `347f7b9550064f5f5b33c6e07f64e85b9657b6f1`</p>
<p>### Release Process Note
`patched_versions` is pre-set to the release (`2026.2.25`). Advisory published with npm release `2026.2.25`.</p>
<p>OpenClaw thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-ghsa-j26j-7qc4-3mrf"/>
  </entry>
</feed>
