What is the CVSS score of CVE-2026-32051?

CVE-2026-32051 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Openclaw are affected by CVE-2026-32051?

OpenClaw versions before 2026.3.1 contain a privilege escalation vulnerability allowing authenticated operators to perform owner-only administrative functions, including gateway and cron management,…. A patch is available.

Is there a public PoC exploit available for CVE-2026-32051?

Yes, a public proof-of-concept exploit is available for CVE-2026-32051. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-32051?

Within 24 hours: Inventory all OpenClaw deployments and identify instances running versions prior to 2026.3.1, particularly those using scoped-token authentication. Within 7 days: Apply vendor patch to upgrade all affected instances to OpenClaw 2026.3.1 or later; verify scoped-token configurations post-upgrade. Within 30 days: Audit recent operator.write activities and administrative function execution logs to identify potential unauthorized privilege escalation; review and re-validate role-based access control policies.

Openclaw CVE-2026-32051

EUVD-2026-13949 HIGH

Incorrect Authorization (CWE-863)

2026-03-21 VulnCheck

GHSA-x2pq-6fc2-wh58

Authentication Bypass Openclaw

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:18 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.3.1

PoC Detected

Mar 23, 2026 - 17:08 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13949

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

CVE Published

Mar 21, 2026 - 00:42 nvd

HIGH 8.8

DescriptionCVE.org

OpenClaw versions prior to 2026.3.1 contain an authorization mismatch vulnerability that allows authenticated callers with operator.write scope to invoke owner-only tool surfaces including gateway and cron through agent runs in scoped-token deployments. Attackers with write-scope access can perform control-plane actions beyond their intended authorization level by exploiting inconsistent owner-only gating during agent execution.

AnalysisAI

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.write scope to escalate privileges and execute owner-only administrative functions including gateway and cron management through agent runs in scoped-token deployments. This is a privilege escalation issue affecting deployments using scoped authentication tokens, where write-level access can be exploited to perform control-plane operations reserved for owners. With a CVSS score of 8.8 and network-accessible attack vector, this represents a significant authorization bypass, though no KEV listing or public exploitation indicators are currently available.

Technical ContextAI

This vulnerability affects OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*), which appears to be a workflow or automation platform with agent-based execution and role-based access control using scoped tokens. The root cause is CWE-863 (Incorrect Authorization), where the system fails to consistently enforce owner-only access controls during agent execution workflows. The authorization logic appears to correctly gate direct API calls but fails to validate permissions when the same privileged operations (gateway configuration, cron job management) are invoked indirectly through agent runs, creating a permission boundary bypass. This type of inconsistent authorization enforcement is common in systems with multiple code paths to the same functionality, where security checks are implemented at the wrong architectural layer.

RemediationAI

Immediately upgrade OpenClaw to version 2026.3.1 or later, which addresses the authorization mismatch in agent run execution as documented in the GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-jr6x-2q95-fh2g. Organizations unable to patch immediately should implement defense-in-depth measures including restricting operator.write scope assignments to only essential personnel, implementing audit logging for all agent run invocations to detect potential exploitation attempts, and reviewing existing agent run configurations for unauthorized owner-level actions. If feasible, temporarily disable agent run functionality for users with only operator.write scope until patching is completed. Organizations not using scoped-token deployments may have reduced exposure but should still prioritize upgrading. Consult the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-authorization-bypass-in-agent-runs-via-owner-only-tool-access for additional technical details on the vulnerability mechanics.