How severe is GHSA-h2vw-ph2c-jvwf?

No CVSS score has been assigned to GHSA-h2vw-ph2c-jvwf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h2vw-ph2c-jvwf?

GHSA-h2vw-ph2c-jvwf affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-h2vw-ph2c-jvwf?

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

How do I detect GHSA-h2vw-ph2c-jvwf 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-h2vw-ph2c-jvwf 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-h2vw-ph2c-jvwf?

O3 pinpoints whether GHSA-h2vw-ph2c-jvwf 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-h2vw-ph2c-jvwf actively exploited in the wild?

No public exploit code has been indexed for GHSA-h2vw-ph2c-jvwf 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 type of vulnerability is GHSA-h2vw-ph2c-jvwf?

GHSA-h2vw-ph2c-jvwf is classified as CWE-441 (CWE-441). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h2vw-ph2c-jvwf published, and has it been updated?

GHSA-h2vw-ph2c-jvwf was published on April 25, 2026 and was last updated on May 19, 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-h2vw-ph2c-jvwf

Fix: openclaw/openclaw@2f06696

GHSA-h2vw-ph2c-jvwf is a CWE-441 vulnerability in openclaw. O3 Security confirms whether GHSA-h2vw-ph2c-jvwf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Workspace dotenv MiniMax host override could redirect credentialed requests

Also known asCVE-2026-44992

Published

Apr 25, 2026

Updated

May 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: >= 2026.4.5, < 2026.4.20
Patched version: 2026.4.20

Impact

A malicious workspace .env could set MINIMAX_API_HOST and redirect credentialed MiniMax requests to an attacker-controlled origin, exposing the MiniMax API key in the outbound Authorization header.

This requires running OpenClaw from an attacker-controlled workspace. Severity is medium.

Fix

OpenClaw now blocks MINIMAX_API_HOST from workspace dotenv injection and removes env-driven URL routing from the affected MiniMax request path.

Fix commit:

2f06696579a1ab0cb5bbbbb6a900414a6b2e3cd1

Release

Fixed in OpenClaw 2026.4.20.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.4.5&&< 2026.4.20	2026.4.20

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

Frequently Asked Questions

## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `>= 2026.4.5, < 2026.4.20` - Patched version: `2026.4.20` ## Impact A malicious workspace `.env` could set `MINIMAX_API_HOST` and redirect credentialed MiniMax requests to an attacker-controlled origin, exposing the MiniMax API key in the outbound `Authorization` header. This requires running OpenClaw from an attacker-controlled workspace. Severity is medium. ## Fix OpenClaw now blocks `MINIMAX_API_HOST` from workspace dotenv injection and removes env-driven URL routing from the affected MiniMax request path

O3 Security · Impact-Aware SCA

Is GHSA-h2vw-ph2c-jvwf in your dependencies?

O3 detects GHSA-h2vw-ph2c-jvwf 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