How severe is GHSA-5847-rm3g-23mw?

No CVSS score has been assigned to GHSA-5847-rm3g-23mw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5847-rm3g-23mw?

GHSA-5847-rm3g-23mw affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-5847-rm3g-23mw?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5847-rm3g-23mw is resolved across your whole dependency graph.

How do I detect GHSA-5847-rm3g-23mw 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-5847-rm3g-23mw 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-5847-rm3g-23mw?

O3 pinpoints whether GHSA-5847-rm3g-23mw 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-5847-rm3g-23mw actively exploited in the wild?

No public exploit code has been indexed for GHSA-5847-rm3g-23mw 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-5847-rm3g-23mw published, and has it been updated?

GHSA-5847-rm3g-23mw was published on March 3, 2026 and was last updated on March 4, 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-5847-rm3g-23mw

OpenClaw has hook auth rate limiter bypass via IPv4-mapped IPv6 client key variants

Published

Mar 3, 2026

Updated

Mar 4, 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

Vulnerability

The hook authentication throttle keyed failed attempts by raw socket remoteAddress text.

IPv4 and IPv4-mapped IPv6 forms of the same client (for example 1.2.3.4 and ::ffff:1.2.3.4) were treated as different clients, allowing separate rate-limit buckets.

Impact

An attacker could split failed hook-auth attempts across both address forms and effectively double the brute-force budget from 20 to 40 attempts per 60-second window.

Affected Components

src/gateway/server-http.ts
src/gateway/auth-rate-limit.ts

Affected Packages / Versions

Package: openclaw (npm)
Vulnerable versions: <= 2026.2.21-2
Patched version (planned next release): 2026.2.22

Remediation

Centralize and reuse canonical client-IP normalization for auth rate-limiting, and use that canonical key for hook auth throttling.

Fix Commit(s)

3284d2eb227e7b6536d543bcf5c3e320bc9d13c5

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.22) so once npm release 2026.2.22 is published, this advisory can be published directly.

OpenClaw thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Vulnerability The hook authentication throttle keyed failed attempts by raw socket `remoteAddress` text. IPv4 and IPv4-mapped IPv6 forms of the same client (for example `1.2.3.4` and `::ffff:1.2.3.4`) were treated as different clients, allowing separate rate-limit buckets. ## Impact An attacker could split failed hook-auth attempts across both address forms and effectively double the brute-force budget from 20 to 40 attempts per 60-second window. ## Affected Components - `src/gateway/server-http.ts` - `src/gateway/auth-rate-limit.ts` ## Affected Packages / Versions - Package: `openc

O3 Security · Impact-Aware SCA

Is GHSA-5847-rm3g-23mw in your dependencies?

O3 detects GHSA-5847-rm3g-23mw 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