OpenClaw: Windows-compatible env override keys could bypass system.run approval binding

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-34426: 0.27% estimated exploitation activity in the next 30 days; percentile 19.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
• CVE-2026-34510: 0.33% estimated exploitation activity in the next 30 days; percentile 26.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Before OpenClaw 2026.4.2, system-run approval binding normalized environment override keys differently from host execution. Windows-compatible keys could be omitted from the approval binding while still being injected at execution time. Impact An approved command could run with attacker-chosen environment overrides that were not represented in the approval binding. This created an approval-integrity gap for affected host-exec flows. Affected Packages / Versions - Package: openclaw (npm) - Affected versions: <= 2026.4.1 - Patched versions: = 2026.4.2 - Latest published npm version: 2026.4.1 Fix Commit(s) - 7eb094a00d80e9f6bf0e62f2c45d3b88ff67c04d — align approval binding with execution-time env-key normalization Release Process Note The fix is present on main and is staged for OpenClaw 2026.4.2. Publish this advisory after the 2026.4.2 npm release is live. Thanks @iskindar for reporting, and thanks @wsparks-vc for coordination.

Published by the source

7 Apr 2026, 18:15 UTC

Last modified by the source

8 Jul 2026, 08:11 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-98ch-45wp-ch47

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-h3x4-hc5v-v2gm

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-98ch-45wp-ch47

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34426

Advisory: OpenClaw: Windows-compatible env override keys could bypass system.run approval binding
IDs: CVE-2026-34426, GHSA-98ch-45wp-ch47
Record: https://patchnext.com/advisories/cve-2026-34426 (revision 4, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.4.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected <= 2026.4.1; fixed in 2026.4.2

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-98ch-45wp-ch47 (OSV record GHSA-98ch-45wp-ch47 lists affected ranges: npm openclaw >=0 <2026.4.2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-h3x4-hc5v-v2gm (OSV record GHSA-h3x4-hc5v-v2gm lists affected ranges: npm openclaw >=0 <2026.3.22 (fixed))
- Verified: https://github.com/advisories/GHSA-98ch-45wp-ch47 (GitHub-reviewed advisory GHSA-98ch-45wp-ch47 lists affected ranges: npm openclaw >=0 <=2026.4.1)

Commands are suggestions: review each one before running it.