GHSA-RM2P-J3R7-4X4J

Vulnerability from github – Published: 2026-03-03 19:50 – Updated: 2026-03-30 13:45
VLAI?
Summary
OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress
Details

Summary

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

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.

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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2026.2.24"
      },
      "package": {
        "ecosystem": "npm",
        "name": "openclaw"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2026.2.25"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-32899"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-03T19:50:26Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Summary\nOpenClaw Slack monitor handled `reaction_*` and `pin_*` non-message events before applying sender-policy checks consistently.\n\nIn affected versions, these events could be added to system-event context even when sender policy would not normally allow them.\n\n### Affected Packages / Versions\n- Package: npm `openclaw`\n- Latest published affected version confirmed: `2026.2.24` (npm latest as of February 26, 2026)\n- Affected range: `\u003c= 2026.2.24`\n- Patched version : `2026.2.25`\n\n### Technical Details\n- `reaction_*` and `pin_*` handlers now route through shared sender authorization (`authorizeSlackSystemEventSender`).\n- Enforced checks now include:\n  - DM `dmPolicy` / `allowFrom`\n  - channel `users` allowlist enforcement for non-DM channels\n  - channel-level allow checks before system-event enqueue\n- Regression coverage added for DM allow/deny and channel-user allowlist deny paths.\n\n### Fix Commit(s)\n- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`\n- `75dfb71e4e8b7c2feba5a8ca662f92ea840e0147`\n\n### Impact\nLow-severity policy-consistency issue in Slack non-message event ingress.\nThis may introduce unexpected reaction/pin context signals from senders outside configured policy.\n\n### Release Process Note\n`patched_versions` is pre-set to planned release `2026.2.25`. Advisory published with npm release `2026.2.25`.\n\nOpenClaw thanks @tdjackey for reporting.",
  "id": "GHSA-rm2p-j3r7-4x4j",
  "modified": "2026-03-30T13:45:13Z",
  "published": "2026-03-03T19:50:26Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-rm2p-j3r7-4x4j"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32899"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openclaw/openclaw/commit/75dfb71e4e8b7c2feba5a8ca662f92ea840e0147"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openclaw/openclaw/commit/aedf62ac7e669a89c7b299201bf6537dc6b12e0e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/openclaw/openclaw"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/openclaw-sender-policy-bypass-in-slack-reaction-and-pin-event-handlers"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "OpenClaw\u0027s Slack reaction/pin sender-policy consistency issue in non-message ingress"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…