How severe is GHSA-rm2p-j3r7-4x4j?

GHSA-rm2p-j3r7-4x4j has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rm2p-j3r7-4x4j?

GHSA-rm2p-j3r7-4x4j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-rm2p-j3r7-4x4j?

Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rm2p-j3r7-4x4j is resolved across your whole dependency graph.

How do I detect GHSA-rm2p-j3r7-4x4j in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rm2p-j3r7-4x4j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rm2p-j3r7-4x4j?

O3 pinpoints whether GHSA-rm2p-j3r7-4x4j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rm2p-j3r7-4x4j actively exploited in the wild?

No public exploit code has been indexed for GHSA-rm2p-j3r7-4x4j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rm2p-j3r7-4x4j?

GHSA-rm2p-j3r7-4x4j has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-rm2p-j3r7-4x4j published, and has it been updated?

GHSA-rm2p-j3r7-4x4j was published on March 3, 2026 and was last updated on March 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-rm2p-j3r7-4x4j

MEDIUM

OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress

Also known asCVE-2026-32899

Published

Mar 3, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk10th percentile+0.16%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.25

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rm2p-j3r7-4x4j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rm2p-j3r7-4x4j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rm2p-j3r7-4x4j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 (`auth

O3 Security · Impact-Aware SCA

Is GHSA-rm2p-j3r7-4x4j in your dependencies?

O3 detects GHSA-rm2p-j3r7-4x4j across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works