NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

OpenClaw's unauthenticated Nostr profile HTTP endpoints allow remote profile/config tamperingGHSA-mv9j-6xhh-g383

MEDIUMFix: openclaw/openclaw@647d929

GHSA-mv9j-6xhh-g383 is a medium-severity (CVSS 6.2) Missing Authentication vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-28450
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-mv9j-6xhh-g383.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk
0.00%0.33%0.66%1.00%0.1%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
openclawnpm
2.8Mdownloads / 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
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.2.12npm install openclaw@2026.2.12

Affected Products

1 product · 1 configurations
Application
openclawopenclaw
< 2026.2.12
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
OpenClaw's unauthenticated Nostr profile HTTP…