GHSA-rm2p-j3r7-4x4j is a medium-severity (CVSS 4.3) CWE-863 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-rm2p-j3r7-4x4j.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-rm2p-j3r7-4x4j plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
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_*andpin_*handlers now route through shared sender authorization (authorizeSlackSystemEventSender).- Enforced checks now include:
- DM
dmPolicy/allowFrom - channel
usersallowlist enforcement for non-DM channels - channel-level allow checks before system-event enqueue
- DM
- Regression coverage added for DM allow/deny and channel-user allowlist deny paths.
Fix Commit(s)
aedf62ac7e669a89c7b299201bf6537dc6b12e0e75dfb71e4e8b7c2feba5a8ca662f92ea840e0147
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.25npm install openclaw@2026.2.25 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rm2p-j3r7-4x4j can be triaged on real exposure rather than presence alone.
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
Is GHSA-rm2p-j3r7-4x4j in your dependencies?
O3 Security finds GHSA-rm2p-j3r7-4x4j across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.