How severe is GHSA-6g25-pc82-vfwp?

No CVSS score has been assigned to GHSA-6g25-pc82-vfwp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6g25-pc82-vfwp?

GHSA-6g25-pc82-vfwp affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6g25-pc82-vfwp?

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

How do I detect GHSA-6g25-pc82-vfwp 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-6g25-pc82-vfwp 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-6g25-pc82-vfwp?

O3 pinpoints whether GHSA-6g25-pc82-vfwp 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-6g25-pc82-vfwp actively exploited in the wild?

No public exploit code has been indexed for GHSA-6g25-pc82-vfwp 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-6g25-pc82-vfwp published, and has it been updated?

GHSA-6g25-pc82-vfwp 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-6g25-pc82-vfwp

OpenClaw: macOS beta onboarding exposed PKCE verifier via OAuth state

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

3.7Mdownloads / week

Description

Summary

The affected surface is the OpenClaw macOS app onboarding flow, and the macOS app is currently in beta. In that beta onboarding flow, Anthropic OAuth used the PKCE code_verifier value as OAuth state, exposing that secret in front-channel URL state.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.24 (latest published npm at triage time)
Affected surface: macOS app beta onboarding path (apps/macos)
Not affected: core CLI/gateway onboarding paths
Patched version : 2026.2.25

Impact

Scope is limited to the macOS beta onboarding OAuth path. Exploitation required obtaining both OAuth authorization artifacts and exposed state values during that flow.

Remediation

OpenClaw removed Anthropic OAuth sign-in from macOS onboarding and now supports setup-token-only Anthropic subscription auth in this path.

Fix Commit(s)

8f3310000a8b0c11eced054c2cdb6fb27803511a

Release Process Note

patched_versions is pre-set to the release (2026.2.25). Advisory published with npm release 2026.2.25.2.25` is published, this advisory is published.

OpenClaw thanks @zdi-disclosures for reporting.

Affected Packages

1 total 1 fixed

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

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.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6g25-pc82-vfwp 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-6g25-pc82-vfwp 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-6g25-pc82-vfwp. 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 affected surface is the OpenClaw macOS app onboarding flow, and the macOS app is currently in **beta**. In that beta onboarding flow, Anthropic OAuth used the PKCE `code_verifier` value as OAuth `state`, exposing that secret in front-channel URL state. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.24` (latest published npm at triage time) - Affected surface: macOS app beta onboarding path (`apps/macos`) - Not affected: core CLI/gateway onboarding paths - Patched version : `2026.2.25` ### Impact Scope is limited to the macOS be

O3 Security · Impact-Aware SCA

Is GHSA-6g25-pc82-vfwp in your dependencies?

O3 detects GHSA-6g25-pc82-vfwp 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