Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.6amended

OpenClaw: Slack interactive callbacks could skip configured sender checks in some shared-workspace flows

CVE-2026-32005GHSA-x2ff-j5c2-ggpr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.2.25), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    <= 2026.2.24
    Fixed in
    2026.2.25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.6 · CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-32005: 0.29% estimated exploitation activity in the next 30 days; percentile 22.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact In shared Slack workspace deployments that rely on sender restrictions (allowFrom, DM policy, or channel user allowlists), some interactive callbacks (blockaction, viewsubmission, viewclosed) could be accepted before full sender authorization checks. In that scenario, an unauthorized workspace member could enqueue system-event text into an active session. This issue did not provide unauthenticated access, cross-gateway isolation bypass, or host-level privilege escalation by itself. Affected Packages / Versions - Package: openclaw (npm) - Vulnerable versions: <= 2026.2.24 - Patched version: 2026.2.25 (planned next npm release) Fix Commit(s) - ce8c67c314b93f570f53c2a9abc124e1e3a54715 Release Process Note patchedversions is pre-set to the release (2026.2.25). Advisory published with npm release 2026.2.25. Trust Model Scope Note OpenClaw does not support adversarial multi-user isolation on a single shared gateway instance. The supported model is one trust boundary per gateway…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-x2ff-j5c2-ggpr

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-x2ff-j5c2-ggpr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32005

Advisory: OpenClaw: Slack interactive callbacks could skip configured sender checks in some shared-workspace flows
IDs: CVE-2026-32005, GHSA-x2ff-j5c2-ggpr
Record: https://patchnext.com/advisories/cve-2026-32005 (revision 3, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.2.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected <= 2026.2.24; fixed in 2026.2.25

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x2ff-j5c2-ggpr (OSV record GHSA-x2ff-j5c2-ggpr lists affected ranges: npm openclaw >=0 <2026.2.25 (fixed))
- Verified: https://github.com/advisories/GHSA-x2ff-j5c2-ggpr (GitHub-reviewed advisory GHSA-x2ff-j5c2-ggpr lists affected ranges: npm openclaw >=0 <=2026.2.24)

Commands are suggestions: review each one before running it.

Loading voting…