<?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-04T23:02:52.531127+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-32899</id>
    <title>BREW-openclaw-cli-CVE-2026-32899 — OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress</title>
    <updated>2026-10-04T23:02:52.578200+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary
OpenClaw Slack monitor handled `reaction_*` and `pin_*` non-message events before applying sender-policy checks consistently.</p>
<p>In affected versions, these events could be added to system-event context even when sender policy would not normally allow them.</p>
<p>### Affected Packages / Versions
- Package: npm `openclaw`
- Latest published affected version confirmed: `2026.2.24` (npm latest as of February 26, 2026)
- Affected range: `&lt;= 2026.2.24`
- Patched version : `2026.2.25`</p>
<p>### Technical Details
- `reaction_*` and `pin_*` handlers now route through shared sender authorization (`authorizeSlackSystemEventSender`).
- Enforced checks now include:
  - DM `dmPolicy` / `allowFrom`
  - channel `users` allowlist enforcement for non-DM channels
  - channel-level allow checks before system-event enqueue
- Regression coverage added for DM allow/deny and channel-user allowlist deny paths.</p>
<p>### Fix Commit(s)
- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`
- `75dfb71e4e8b7c2feba5a8ca662f92ea840e0147`</p>
<p>### Impact
Low-severity policy-consistency issue in Slack non-message event ingress.
This may introduce unexpected reaction/pin context signals from senders outside configured policy.</p>
<p>### Release Process Note
`patched_versions` is pre-set to planned 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-cve-2026-32899"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-14830</id>
    <title>cnvd-2026-14830</title>
    <updated>2026-10-04T23:02:52.578271+00:00</updated>
    <content>cnvd-2026-14830</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-14830"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329462</id>
    <title>EUVD-2026-329462</title>
    <updated>2026-10-04T23:02:52.578289+00:00</updated>
    <content>EUVD-2026-329462</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329462"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32899</id>
    <title>fkie_cve-2026-32899</title>
    <updated>2026-10-04T23:02:52.578302+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw versions prior to 2026.2.25 fail to consistently apply sender-policy checks to reaction_* and pin_* non-message events before adding them to system-event context. Attackers can bypass configured DM policies and channel user allowlists to inject unauthorized reaction and pin events from restricted senders.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32899"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rm2p-j3r7-4x4j</id>
    <title>GHSA-rm2p-j3r7-4x4j — OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress</title>
    <updated>2026-10-04T23:02:52.578324+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary
OpenClaw Slack monitor handled `reaction_*` and `pin_*` non-message events before applying sender-policy checks consistently.</p>
<p>In affected versions, these events could be added to system-event context even when sender policy would not normally allow them.</p>
<p>### Affected Packages / Versions
- Package: npm `openclaw`
- Latest published affected version confirmed: `2026.2.24` (npm latest as of February 26, 2026)
- Affected range: `&lt;= 2026.2.24`
- Patched version : `2026.2.25`</p>
<p>### Technical Details
- `reaction_*` and `pin_*` handlers now route through shared sender authorization (`authorizeSlackSystemEventSender`).
- Enforced checks now include:
  - DM `dmPolicy` / `allowFrom`
  - channel `users` allowlist enforcement for non-DM channels
  - channel-level allow checks before system-event enqueue
- Regression coverage added for DM allow/deny and channel-user allowlist deny paths.</p>
<p>### Fix Commit(s)
- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`
- `75dfb71e4e8b7c2feba5a8ca662f92ea840e0147`</p>
<p>### Impact
Low-severity policy-consistency issue in Slack non-message event ingress.
This may introduce unexpected reaction/pin context signals from senders outside configured policy.</p>
<p>### Release Process Note
`patched_versions` is pre-set to planned 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/ghsa-rm2p-j3r7-4x4j"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0542</id>
    <title>WID-SEC-W-2026-0542 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-04T23:02:52.578357+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Dateien zu manipulieren, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0542"/>
  </entry>
</feed>
