Skip to content

OpenClaw: Unified root-bound write hardening for browser output and related path-boundary flows

Moderate severity GitHub Reviewed Published Mar 3, 2026 in openclaw/openclaw • Updated Mar 18, 2026

Package

npm openclaw (npm)

Affected versions

<= 2026.3.1

Patched versions

2026.3.2

Description

Summary

A path-confinement bypass in browser output handling allowed writes outside intended roots in openclaw versions up to and including 2026.3.1.

The fix unifies root-bound, file-descriptor-verified write semantics and canonical path-boundary validation across browser output and related install/skills write paths.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published npm version at triage time: 2026.3.1
  • Affected range: <= 2026.3.1
  • Patched release: 2026.3.2 (released)

Fix Commit(s)

  • 104d32bb64cdf19d5e77f70553a511a2ae90ad1c

Technical Notes

  • Browser output writes now use root-bound, fd/inode-verified commit flow.
  • Install + skills path checks now share canonical in-base validation to reduce drift and close equivalent escape surfaces.
  • Added regression coverage for symlink-rebind and root-bound source-path write behavior.

References

@steipete steipete published to openclaw/openclaw Mar 3, 2026
Published to the GitHub Advisory Database Mar 3, 2026
Reviewed Mar 3, 2026
Last updated Mar 18, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(3rd percentile)

Weaknesses

Improper Link Resolution Before File Access ('Link Following')

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. Learn more on MITRE.

Time-of-check Time-of-use (TOCTOU) Race Condition

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. Learn more on MITRE.

CVE ID

CVE-2026-22180

GHSA ID

GHSA-3pxq-f3cp-jmxp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.