How severe is GHSA-ppwq-6v66-5m6j?

No CVSS score has been assigned to GHSA-ppwq-6v66-5m6j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ppwq-6v66-5m6j?

GHSA-ppwq-6v66-5m6j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-ppwq-6v66-5m6j?

Update openclaw to 2026.3.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ppwq-6v66-5m6j is resolved across your whole dependency graph.

How do I detect GHSA-ppwq-6v66-5m6j 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-ppwq-6v66-5m6j 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-ppwq-6v66-5m6j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ppwq-6v66-5m6j can be triaged on real exposure rather than presence alone.

Is GHSA-ppwq-6v66-5m6j actively exploited in the wild?

No public exploit code has been indexed for GHSA-ppwq-6v66-5m6j 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-ppwq-6v66-5m6j?

GHSA-ppwq-6v66-5m6j has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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-ppwq-6v66-5m6j?

GHSA-ppwq-6v66-5m6j is classified as CWE-312 (CWE-312). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-ppwq-6v66-5m6j published, and has it been updated?

GHSA-ppwq-6v66-5m6j was published on March 26, 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-ppwq-6v66-5m6j — openclaw

Fix: openclaw/openclaw@f020226

GHSA-ppwq-6v66-5m6j is a CWE-312 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw Exposes Credentials Embedded in baseUrl Fields via config.get and channels.status

Also known asCVE-2026-35644

Published

Mar 26, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 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-ppwq-6v66-5m6j.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% 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.0Mdownloads / week

Description

Summary

Read-scoped gateway snapshots could expose credentials embedded in channel baseUrl and related endpoint fields.

Affected Packages / Versions

Package: openclaw (npm)
Affected: < 2026.3.22
Fixed: >= 2026.3.22
Latest released tag checked: v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87)
Latest published npm version checked: 2026.3.23-2

Fix Commit(s)

f0202264d0de7ad345382b9008c5963bcefb01b7

Release Status

The fix shipped in v2026.3.22 and remains present in v2026.3.23 and v2026.3.23-2.

Code-Level Confirmation

src/channels/account-snapshot-fields.ts now strips URL userinfo from channel status snapshot fields.
src/config/redact-snapshot.ts now redacts credential-bearing baseUrl and httpUrl fields while preserving safe context.

OpenClaw thanks @zpbrent for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.22`npm install openclaw@2026.3.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.3.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ppwq-6v66-5m6j 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-ppwq-6v66-5m6j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-ppwq-6v66-5m6j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Read-scoped gateway snapshots could expose credentials embedded in channel baseUrl and related endpoint fields. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: < 2026.3.22 - Fixed: >= 2026.3.22 - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2` ## Fix Commit(s) - `f0202264d0de7ad345382b9008c5963bcefb01b7` ## Release Status The fix shipped in `v2026.3.22` and remains present in `v2026.3.23` and `v2026.3.23-2`. ## Code-Level Confirmation - src/channels/account-snap

O3 Security · Impact-Aware SCA

Is GHSA-ppwq-6v66-5m6j in your dependencies?

O3 Security finds GHSA-ppwq-6v66-5m6j 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