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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6g25-pc82-vfwp can be triaged on real exposure rather than presence alone.

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.

What is the EPSS score for GHSA-6g25-pc82-vfwp?

GHSA-6g25-pc82-vfwp has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th 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-6g25-pc82-vfwp?

GHSA-6g25-pc82-vfwp is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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 July 8, 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

Not in CISA KEV

GHSA-6g25-pc82-vfwp — openclaw

Fix: openclaw/openclaw@8f33100

GHSA-6g25-pc82-vfwp is a Information Exposure vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: macOS beta onboarding exposed PKCE verifier via OAuth state

Also known asCVE-2026-3691

Published

Mar 3, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

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.

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

3.1Mdownloads / 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`npm install openclaw@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6g25-pc82-vfwp can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-6g25-pc82-vfwp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works