How severe is GHSA-jp4j-q5fc-58gv?

No CVSS score has been assigned to GHSA-jp4j-q5fc-58gv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jp4j-q5fc-58gv?

GHSA-jp4j-q5fc-58gv affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jp4j-q5fc-58gv?

Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jp4j-q5fc-58gv is resolved across your whole dependency graph.

How do I detect GHSA-jp4j-q5fc-58gv 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-jp4j-q5fc-58gv 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-jp4j-q5fc-58gv?

O3 pinpoints whether GHSA-jp4j-q5fc-58gv 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-jp4j-q5fc-58gv actively exploited in the wild?

No public exploit code has been indexed for GHSA-jp4j-q5fc-58gv 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.

When was GHSA-jp4j-q5fc-58gv published, and has it been updated?

GHSA-jp4j-q5fc-58gv was published on March 31, 2026 and was last updated on April 1, 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-jp4j-q5fc-58gv

OpenClaw's Discord component interaction ingress skips guild/channel policy enforcement

Published

Mar 31, 2026

Updated

Apr 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Discord button and component interaction ingress did not consistently reapply the same guild and channel policy gates used for normal inbound messages.

Impact

Users could trigger privileged component actions from contexts that should have been blocked by Discord channel policy.

Affected Component

extensions/discord/src/monitor/agent-components.ts

Fixed Versions

Affected: >= 2026.2.14, <= 2026.3.24
Patched: >= 2026.3.28
Latest stable 2026.3.28 contains the fix.

Fix

Fixed by commit 511093d4b3 (Discord: apply component interaction policy gates).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.2.14&&< 2026.3.28	2026.3.28

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.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jp4j-q5fc-58gv 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-jp4j-q5fc-58gv 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-jp4j-q5fc-58gv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Discord button and component interaction ingress did not consistently reapply the same guild and channel policy gates used for normal inbound messages. ## Impact Users could trigger privileged component actions from contexts that should have been blocked by Discord channel policy. ## Affected Component `extensions/discord/src/monitor/agent-components.ts` ## Fixed Versions - Affected: `>= 2026.2.14, <= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `511093d4b3` (`Discord: apply component interaction policy gates`).

O3 Security · Impact-Aware SCA

Is GHSA-jp4j-q5fc-58gv in your dependencies?

O3 detects GHSA-jp4j-q5fc-58gv 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