Incorrect Authorization Affecting openclaw package, versions <2026.8.1


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.21% (10th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Incorrect Authorization vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JS-OPENCLAW-20186835
  • published28 Sept 2026
  • disclosed26 Sept 2026
  • creditUnknown

Introduced: 26 Sep 2026

NewCVE-2026-100529  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade openclaw to version 2026.8.1 or higher.

Overview

openclaw is a 🦞 OpenClaw — Personal AI Assistant

Affected versions of this package are vulnerable to Incorrect Authorization via glob metacharacter interpretation and node display name reuse in file-transfer allow-always approvals. When an operator approves a file-transfer request, a later agent request can reuse that standing grant to access sibling paths or different nodes that were never shown in the original approval. Literal path characters in the approved path can subsequently be interpreted as glob syntax, and node-specific grants can be reused by any other node sharing the same display name, broadening durable read or write access beyond the operator's intended scope.

Note: Exploitation requires a prior operator allow-always approval and a matching widened target (a sibling path reachable via glob expansion, or a different node with the same display name).

Workaround

Avoid using allow-always for file-transfer requests containing glob metacharacters, and ensure all nodes have unique display names. Remove and recreate any existing standing file-transfer grants after upgrading.

References

CVSS Base Scores

version 4.0
version 3.1