Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-xxvh-5hwj-42pp

MediumCVSS 4.8 / 10
Published Feb 18, 2026·Last modified Feb 20, 2026
Affected Components(0)

No affected components available

Description

Description

normalizeForHash in src/agents/sandbox/config-hash.ts recursively sorted arrays that contained only primitive values. This made order-sensitive sandbox configuration arrays hash to the same value even when order changed.

In OpenClaw sandbox flows, this hash is used to decide whether existing sandbox containers should be recreated. As a result, order-only config changes (for example Docker dns and binds array order) could be treated as unchanged and stale containers could be reused.

This is a configuration integrity issue affecting sandbox recreation behavior.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected: <=2026.2.14
  • Patched (planned next release): >=2026.2.15
  • Latest published npm version at triage time (2026-02-16): 2026.2.14

Remediation

Array ordering is now preserved during hash normalization; only object key ordering remains normalized for deterministic hashing.

Fix Commit(s)

  • 41ded303b4f6dae5afa854531ff837c3276ad60b

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.15) so after npm publish, the advisory can be published directly without reopening version metadata edits.

Thanks @kexinoh ( of Tencent zhuque Lab, by https://github.com/Tencent/AI-Infra-Guard) for reporting.

Risk Scores
Base Score
4.8

The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
1.1

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.16%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard