How severe is GHSA-f3h5-h452-vp3j?

No CVSS score has been assigned to GHSA-f3h5-h452-vp3j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f3h5-h452-vp3j?

GHSA-f3h5-h452-vp3j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-f3h5-h452-vp3j?

Update openclaw to 2026.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f3h5-h452-vp3j is resolved across your whole dependency graph.

How do I detect GHSA-f3h5-h452-vp3j 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-f3h5-h452-vp3j 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-f3h5-h452-vp3j?

O3 pinpoints whether GHSA-f3h5-h452-vp3j 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-f3h5-h452-vp3j actively exploited in the wild?

No public exploit code has been indexed for GHSA-f3h5-h452-vp3j 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-f3h5-h452-vp3j published, and has it been updated?

GHSA-f3h5-h452-vp3j was published on April 17, 2026 and was last updated on April 17, 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-f3h5-h452-vp3j

OpenClaw: Nostr profile mutation routes allowed operator.write config persistence

Published

Apr 17, 2026

Updated

Apr 17, 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

3.7Mdownloads / week

Description

Summary

Nostr profile mutation routes allowed operator.write config persistence.

Affected Packages / Versions

Package: openclaw
Ecosystem: npm
Affected versions: < 2026.4.10
Patched versions: >= 2026.4.10

Impact

Nostr plugin HTTP profile routes could persist profile config through a path that did not require admin authority.

Technical Details

The fix requires operator.admin scope for Nostr profile mutation routes.

Fix

The issue was fixed in #63553. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.

Fix Commit(s)

6517c700de9bb0ee11b41ab625ef3b63d01b6083
PR: #63553

Release Process Note

Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @zpbrent and @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary Nostr profile mutation routes allowed operator.write config persistence. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `< 2026.4.10` - Patched versions: `>= 2026.4.10` ## Impact Nostr plugin HTTP profile routes could persist profile config through a path that did not require admin authority. ## Technical Details The fix requires `operator.admin` scope for Nostr profile mutation routes. ## Fix The issue was fixed in #63553. The first stable tag containing the fix is `v2026.4.10`, and `[email protected]` includes the fix. ## Fix

O3 Security · Impact-Aware SCA

Is GHSA-f3h5-h452-vp3j in your dependencies?

O3 detects GHSA-f3h5-h452-vp3j 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