How severe is GHSA-h5hg-h7rr-gpf3?

No CVSS score has been assigned to GHSA-h5hg-h7rr-gpf3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h5hg-h7rr-gpf3?

GHSA-h5hg-h7rr-gpf3 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-h5hg-h7rr-gpf3?

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

How do I detect GHSA-h5hg-h7rr-gpf3 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-h5hg-h7rr-gpf3 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.

Is GHSA-h5hg-h7rr-gpf3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h5hg-h7rr-gpf3 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-h5hg-h7rr-gpf3?

GHSA-h5hg-h7rr-gpf3 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th 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-h5hg-h7rr-gpf3?

GHSA-h5hg-h7rr-gpf3 is classified as CWE-472 (CWE-472). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h5hg-h7rr-gpf3 published, and has it been updated?

GHSA-h5hg-h7rr-gpf3 was published on April 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

OpenClaw: Node browser proxy `allowProfiles` bypass through persistent profile mutation and runtime profile selectionGHSA-h5hg-h7rr-gpf3

Fix: openclaw/openclaw@eac9350

GHSA-h5hg-h7rr-gpf3 is a CWE-472 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-41353

Published

Apr 3, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-h5hg-h7rr-gpf3.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.27%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

132other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.4Mdownloads / week

Description

Summary

Node browser proxy allowProfiles bypass through persistent profile mutation and runtime profile selection

Current Maintainer Triage

Status: open
Normalized severity: high
Assessment: Real released allowProfiles bypass through profile mutation and runtime profile selection, fixed and shipped in v2026.3.22+, so keep open for publish rather than close.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.13-1
Patched versions: >= 2026.3.22
First stable tag containing the fix: v2026.3.22

Fix Commit(s)

eac93507c36ccd0c359fba18fa466ef6448be8a5 — 2026-03-23T00:56:44-07:00

Release Process Note

The fix is already present in released version 2026.3.22.
This draft looks ready for final maintainer disposition or publication, not additional code-fix work.

Thanks @smaeljaish771 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`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.3.22

range

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-h5hg-h7rr-gpf3 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.

Frequently Asked Questions

## Summary Node browser proxy `allowProfiles` bypass through persistent profile mutation and runtime profile selection ## Current Maintainer Triage - Status: open - Normalized severity: high - Assessment: Real released allowProfiles bypass through profile mutation and runtime profile selection, fixed and shipped in v2026.3.22+, so keep open for publish rather than close. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.13-1` - Patched versions: `>= 2026.3.22` - First stable tag containing the fix: `v

O3 Security · Impact-Aware SCA

Is GHSA-h5hg-h7rr-gpf3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works