CVE-2026-100579
Received Received - Intake

Identity Spoofing in OpenClaw npm Package

Publication date: 2026-09-26

Last updated on: 2026-09-26

Assigner: VulnCheck

Description
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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-26
Last Modified
2026-09-26
Generated
2026-09-26
AI Q&A
2026-09-26
EPSS Evaluated
N/A
NVD
CVE-2026-100579
EUVD
EUVD-2026-87472

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

OpenClaw before version 2026.7.1 has an authentication bypass flaw where a write-scoped caller can spoof another user's identity by manipulating the message.action field. This affects identity-bearing Gateway deployments that trust caller identity. The real caller's permissions may be bypassed, allowing unauthorized actions depending on the channel and target account settings.

Detection Guidance

To detect this vulnerability, check the version of the openclaw npm package. If the version is prior to 2026.7.1, the system is vulnerable. Run: npm list openclaw or npm view openclaw version. Additionally, review Gateway deployments using identity-bearing authentication modes for unauthorized actions under spoofed identities.

Impact Analysis

Impact depends on the enabled channel, action performed, and target account permissions. A malicious actor could perform unauthorized operations under a spoofed identity, potentially accessing or modifying data they shouldn't. Shared-secret token and password callers are not affected as they are fully trusted operators.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling unauthorized access or actions under spoofed identities. GDPR requires strict access controls and data protection measures, while HIPAA mandates safeguards for protected health information. The spoofing risk may lead to unauthorized data exposure or modifications, violating confidentiality and integrity requirements in these regulations.

Mitigation Strategies
  • Upgrade the OpenClaw npm package to version 2026.7.1 or later to patch the vulnerability.
  • Restrict access to the message.action field to administrators only.
  • Disable sensitive channel actions that rely on requester identity verification.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-100579. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart