Authorization Bypass Through User-Controlled Key Affecting openclaw package, versions <2026.7.1-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.23% (13th 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 IDSNYK-MINIMOSLATEST-OPENCLAW-20371289
  • published2 Oct 2026
  • disclosed26 Sept 2026

Introduced: 26 Sep 2026

NewCVE-2026-100579  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

Upgrade Minimos:latest openclaw to version 2026.7.1-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openclaw package and not the openclaw package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

OpenClaw (npm package 'openclaw') before 2026.7.1 incorrectly trusts requester provenance in message.action. In identity-bearing Gateway deployments (authentication modes that honor caller identity and narrower operator scopes), a write-scoped caller can supply another sender's identifier to the channel authorization checks and invoke a channel action under that spoofed requester identity, reaching operations the channel adapter would have denied to the real caller. Practical impact depends on the enabled channel, the action, and the target account's permissions. Shared-secret token and password callers are full trusted operators under OpenClaw's security model and are out of scope. The issue is fixed in 2026.7.1; as a workaround, restrict message.action to administrators and disable sensitive channel actions that rely on requester identity.

CVSS Base Scores

version 3.1