OpenClaw before 2026.7.1 Authentication Bypass via Spoofed Requester (CVE-2026-100579) | HOL Guard CVE

High · CVSS 7.2CVE-2026-100579

OpenClaw before 2026.7.1 Authentication Bypass via Spoofed Requester

Answer in brief

CVE-2026-100579 records a High severity (CVSS 7.2) vulnerability in OpenClaw before 2026.7.1 Authentication Bypass via Spoofed Requester. The current sources do not mark it as known exploited. The current feed maps OpenClaw/OpenClaw (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 26, 2026Updated Sep 26, 2026Source checked Sep 26, 2026First seen by HOL Sep 26, 2026Material review Sep 26, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.2
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenClaw/OpenClaw (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenClaw/OpenClawgeneric	>=0 <2026.7.1	2026.7.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenClaw/OpenClaw.
Review the reported fix. Update OpenClaw/OpenClaw to 2026.7.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 26, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.