CVE-2026-32899

OpenClaw Slack monitor handled reaction_* and pin_* non-message events before applying sender-policy checks consistently.

In affected versions, these events could be added to system-event context even when sender policy would not normally allow them.

Affected Packages / Versions

• Package: npm openclaw
• Latest published affected version confirmed: 2026.2.24 (npm latest as of February 26, 2026)
• Affected range: <= 2026.2.24
• Patched version : 2026.2.25

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.

Fix Commit(s)

• aedf62ac7e669a89c7b299201bf6537dc6b12e0e
• 75dfb71e4e8b7c2feba5a8ca662f92ea840e0147

Release Process Note

patched_versions is pre-set to planned release 2026.2.25. Advisory published with npm release 2026.2.25.

OpenClaw thanks @tdjackey for reporting.

Low-severity policy-consistency issue in Slack non-message event ingress.
This may introduce unexpected reaction/pin context signals from senders outside configured policy.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-32899 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.25); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32899? CVE-2026-32899 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.24. It is fixed in 2026.2.25. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-32899? CVE-2026-32899 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32899? openclaw (npm) versions <= 2026.2.24 is affected.
4. Is there a fix for CVE-2026-32899? Yes. CVE-2026-32899 is fixed in 2026.2.25. Upgrade to this version or later.
5. Is CVE-2026-32899 exploitable, and should I be worried? Whether CVE-2026-32899 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32899 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32899? Upgrade openclaw to 2026.2.25 or later.