# CVE-2026-100579: OpenClaw authorization bypass via spoofed requester identity

Source: https://junglewise.ai/threats/cve-2026-100579-openclaw-npm-package-openclaw-before-2026-7-1-incorrectly-trusts  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-26. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-100579 · Severity: high · CVSS 7.6 · Published 2026-09-26

OpenClaw is an npm package used for managing gateway authentication and channel authorization in distributed systems. A vulnerability allows authenticated users with write permissions to impersonate other users and invoke channel actions they should not have access to, potentially leading to unauthorized data modification or access to sensitive operations. The issue affects identity-bearing Gateway deployments where caller identity matters; organizations using shared-secret tokens or passwords are unaffected. This has been patched in version 2026.7.1.

Technologies: [Openclaw](https://junglewise.ai/threats/technologies/openclaw). Vendors: [Openclaw](https://junglewise.ai/threats/vendors/openclaw).

## Quick answers

**Is CVE-2026-100579 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-100579 being exploited in the wild.

**How severe is CVE-2026-100579?** High severity, with a CVSS score of 7.6, published 26 September 2026.

**Which products and versions are affected?** Openclaw before 2026.7.1.

**Is there a fix for CVE-2026-100579?** A patch was published on 2026-09-26: version 2026.7.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-100579 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-100579?** Check whether you run Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an authorization bypass (CWE-639, CWE-863) in the message.action handler where requester provenance is not properly validated. A write-scoped caller in an identity-bearing Gateway deployment can supply a spoofed sender identifier to bypass channel authorization checks. The attack requires network access and low privileges (write scope); no user interaction is needed. An attacker gains the ability to invoke channel actions under a different user's identity, reaching operations normally denied to their actual privileges.

## Affected products

- OpenClaw openclaw before 2026.7.1

## Timeline

- 2026-09-26: disclosed
- 2026-09-26: patched: version 2026.7.1

## References

- [https://github.com/openclaw/openclaw/security/advisories/GHSA-4wvr-f35r-f8w4](https://github.com/openclaw/openclaw/security/advisories/GHSA-4wvr-f35r-f8w4)
- [https://www.vulncheck.com/advisories/openclaw-before-2026.7.1-authentication-bypass-via-spoofed-requester](https://www.vulncheck.com/advisories/openclaw-before-2026.7.1-authentication-bypass-via-spoofed-requester)

## Related threats

- [OpenClaw incorrect authorization in mcp.app.view method](https://junglewise.ai/threats/cve-2026-102807-openclaw-before-2026-9-4-contains-an-incorrect-authorization)
- [OpenClaw incorrect authorization in Gateway media root allowlist](https://junglewise.ai/threats/cve-2026-102806-openclaw-before-2026-9-5-contains-an-incorrect-authorization)
- [OpenClaw exec approval bypass in Google Meet node commands](https://junglewise.ai/threats/cve-2026-100599-openclaw-versions-2026-5-1-through-2026-7-0-fail-to-apply-the)
- [OpenClaw Signal approval reaction binding logic error](https://junglewise.ai/threats/cve-2026-100598-openclaw-npm-package-openclaw-before-2026-7-1-incorrectly-binds)
- [OpenClaw time-of-check time-of-use race condition in filesystem operations](https://junglewise.ai/threats/cve-2026-100597-openclaw-npm-package-openclaw-before-2026-7-1-is-vulnerable-to-a)