How severe is GHSA-mv9j-6xhh-g383?

GHSA-mv9j-6xhh-g383 has a CVSS score of 6.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-mv9j-6xhh-g383?

GHSA-mv9j-6xhh-g383 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-mv9j-6xhh-g383?

Update openclaw to 2026.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mv9j-6xhh-g383 is resolved across your whole dependency graph.

How do I detect GHSA-mv9j-6xhh-g383 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-mv9j-6xhh-g383 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-mv9j-6xhh-g383?

O3 pinpoints whether GHSA-mv9j-6xhh-g383 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-mv9j-6xhh-g383 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mv9j-6xhh-g383 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-mv9j-6xhh-g383?

GHSA-mv9j-6xhh-g383 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th 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-mv9j-6xhh-g383 published, and has it been updated?

GHSA-mv9j-6xhh-g383 was published on February 17, 2026 and was last updated on March 6, 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-mv9j-6xhh-g383

MEDIUM

OpenClaw's unauthenticated Nostr profile HTTP endpoints allow remote profile/config tampering

Also known asCVE-2026-28450

Published

Feb 17, 2026

Updated

Mar 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile+0.22%

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

The OpenClaw Nostr channel plugin (optional, disabled by default, installed separately) exposes profile management HTTP endpoints under /api/channels/nostr/:accountId/profile (GET/PUT) and /api/channels/nostr/:accountId/profile/import (POST). In affected versions, these routes were dispatched via the gateway plugin HTTP layer without requiring gateway authentication, allowing unauthenticated remote callers to read or mutate the Nostr profile and persist changes to the gateway config. Profile updates are also published as a signed Nostr kind:0 event using the bot's private key.

Deployments that do not have the Nostr plugin installed and enabled are not impacted.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.9
Fixed versions: >= 2026.2.12
Scope note: only affects deployments with the optional @openclaw/nostr plugin installed and enabled

Details

This is exploitable when the gateway HTTP port is reachable beyond localhost (for example: bound to 0.0.0.0, exposed on a LAN, behind a reverse proxy, or via Tailscale Funnel/Serve).

Unauthenticated callers could update the Nostr profile and persist the new profile in the gateway config.

Mitigation

Upgrade to openclaw 2026.2.12 or later.

As a temporary mitigation, restrict gateway HTTP exposure (bind loopback-only and/or enforce network-layer access controls) until upgraded.

Fix

Gateway now requires gateway authentication for plugin HTTP requests under /api/channels/* before dispatching to plugin handlers.

Fix commit(s):

647d929c9d0fd114249230d939a5cb3b36dc70e7

Thanks @simecek for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary The OpenClaw Nostr channel plugin (optional, disabled by default, installed separately) exposes profile management HTTP endpoints under `/api/channels/nostr/:accountId/profile` (GET/PUT) and `/api/channels/nostr/:accountId/profile/import` (POST). In affected versions, these routes were dispatched via the gateway plugin HTTP layer without requiring gateway authentication, allowing unauthenticated remote callers to read or mutate the Nostr profile and persist changes to the gateway config. Profile updates are also published as a signed Nostr kind:0 event using the bot's private key.

O3 Security · Impact-Aware SCA

Is GHSA-mv9j-6xhh-g383 in your dependencies?

O3 detects GHSA-mv9j-6xhh-g383 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