CVE-2026-53864: OpenClaw < 2026.5.26 - Insufficient Environment Variable Sanitization in Node.js Control Variables

Published Jun 16, 2026
·
Updated

Summary

Host environment sanitizer missed two Node.js control variables. In affected versions, a lower-trust env source such as a workspace .env, tool env override, or skill env block could pass Node.js control variables through the shared sanitizer.

This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.

Impact

When the affected feature is enabled and reachable, this could influence a later Node.js child process or coverage output path when that process is launched under the accepted environment. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.

Patched Versions

The first stable patched version is 2026.5.26.

Mitigations

avoid inheriting workspace or tool-supplied env values from untrusted repositories until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

Other sources

OpenClaw before 2026.5.26 contains an insufficient sanitization vulnerability in the host environment sanitizer that allows Node.js control variables to bypass validation. Attackers with access to workspace .env files, tool environment overrides, or skill environment blocks can pass malicious Node.js control variables to influence child processes or coverage output paths.

MITRE

Affected Software

5 affected componentsFixes available
OpenClaw OpenClaw<2026.5.26
OpenClaw Openclaw Node.js<2026.5.26
OpenClaw Openclaw Node.js=2026.5.26-beta1
OpenClaw Openclaw Node.js=2026.5.26-beta2
npm/openclaw<=2026.5.22
2026.5.26

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/openclaw to a version that resolves this vulnerability.

    Fixed in 2026.5.26
  2. Configuration

    Disable the affected host environment feature (the OpenClaw feature that ingests workspace/tool/skill environment blocks and passes Node.js control variables) when it is not required.

    OpenClaw affected_feature_enabled = false
  3. Compensating control

    Until patched, avoid inheriting workspace or tool-supplied environment values from untrusted repositories. Keep channel and tool allowlists narrow and avoid sharing a single Gateway between mutually untrusted users to reduce the risk that lower-trust inputs can influence Node.js child processes or coverage paths.

Event History

Jun 16, 2026
CVE Published
via MITRE·06:05 PM
Data Sourced
via MITRE·06:05 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software
Jun 18, 2026
Advisory Published
via GitHub·01:02 PM
Data Sourced
via GitHub·01:02 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53864?

CVE-2026-53864 has a severity rating of 8.1, categorized as high.

2

How do I fix CVE-2026-53864?

To fix CVE-2026-53864, upgrade OpenClaw to version 2026.5.26 or later.

3

What kind of attacks are possible with CVE-2026-53864?

CVE-2026-53864 allows attackers to bypass validation of Node.js control variables through insufficient sanitization.

4

Who is affected by CVE-2026-53864?

Users of OpenClaw versions prior to 2026.5.26 are affected by CVE-2026-53864.

5

How does CVE-2026-53864 impact Node.js applications?

CVE-2026-53864 can lead to security breaches in Node.js applications by allowing malicious input through environment variables.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203