How severe is GHSA-hff7-ccv5-52f8?

No CVSS score has been assigned to GHSA-hff7-ccv5-52f8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hff7-ccv5-52f8?

GHSA-hff7-ccv5-52f8 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-hff7-ccv5-52f8?

Update openclaw to 2026.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hff7-ccv5-52f8 is resolved across your whole dependency graph.

How do I detect GHSA-hff7-ccv5-52f8 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-hff7-ccv5-52f8 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-hff7-ccv5-52f8?

O3 pinpoints whether GHSA-hff7-ccv5-52f8 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-hff7-ccv5-52f8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hff7-ccv5-52f8 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-hff7-ccv5-52f8?

GHSA-hff7-ccv5-52f8 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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.

What type of vulnerability is GHSA-hff7-ccv5-52f8?

GHSA-hff7-ccv5-52f8 is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hff7-ccv5-52f8 published, and has it been updated?

GHSA-hff7-ccv5-52f8 was published on March 3, 2026 and was last updated on March 24, 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-hff7-ccv5-52f8

OpenClaw's gateway tokenless Tailscale auth applied to HTTP routes

Also known asCVE-2026-32045

Published

Mar 3, 2026

Updated

Mar 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk32th percentile+0.31%

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.4Mdownloads / week

Description

Summary

When tokenless Tailscale auth is enabled, OpenClaw should only allow forwarded-header auth for Control UI websocket authentication on trusted hosts. In affected versions, that tokenless path could also be used by HTTP gateway auth call sites, which could bypass token/password requirements for HTTP routes in trusted-network deployments.

Affected Packages / Versions

Package: openclaw (npm)
Affected range: <= 2026.2.19-2 (latest published npm version as of February 21, 2026)
Patched in: planned 2026.2.21 release

Impact

Deployments relying on token/password for HTTP gateway routes could be downgraded to tokenless behavior when Tailscale header auth is enabled. This weakens expected HTTP route authentication boundaries even in trusted-host network setups.

Per SECURITY.md, this does not affect the recommended setup: keep the Gateway loopback-only (or otherwise within a trusted host/network boundary), use Tailscale serve/funnel for remote access, and keep tokenless Tailscale auth scoped to Control UI websocket login.

Fix

Added an explicit auth-surface gate (allowTailscaleHeaderAuth, default false) in gateway auth.
Enabled tokenless Tailscale header auth only for Control UI websocket authentication.
Kept HTTP gateway auth call sites on token/password auth paths.
Added regression coverage for HTTP-vs-websocket behavior and Tailscale header handling.

Fix Commit(s)

356d61aacfa5b0f1d5830716ec59d70682a3e7b8

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.21) so once npm release is published, this advisory can be published directly without further field edits.

OpenClaw thanks @zpbrent for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

### Summary When tokenless Tailscale auth is enabled, OpenClaw should only allow forwarded-header auth for Control UI websocket authentication on trusted hosts. In affected versions, that tokenless path could also be used by HTTP gateway auth call sites, which could bypass token/password requirements for HTTP routes in trusted-network deployments. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected range: `<= 2026.2.19-2` (latest published npm version as of February 21, 2026) - Patched in: planned `2026.2.21` release ### Impact Deployments relying on token/password for HT

O3 Security · Impact-Aware SCA

Is GHSA-hff7-ccv5-52f8 in your dependencies?

O3 detects GHSA-hff7-ccv5-52f8 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