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

CVE-2026-32895 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

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

CVE-2026-32895 presents moderate security risk, a incorrect authorization vulnerability rated CVSS 5.4. Attackers could gain access beyond their authorized level.. A patch is available.

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

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

How to fix or mitigate CVE-2026-32895?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Vendor patch is available.

Openclaw CVE-2026-32895

EUVD-2026-13970 MEDIUM

Incorrect Authorization (CWE-863)

2026-03-21 VulnCheck

GHSA-xgwg-m42c-8q62

Authentication Bypass Openclaw

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

PoC Detected

Mar 23, 2026 - 19:47 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13970

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

Patch released

Mar 21, 2026 - 01:00 nvd

Patch available

CVE Published

Mar 21, 2026 - 00:42 nvd

MEDIUM 5.4

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on openclaw (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.26.

DescriptionCVE.org

OpenClaw versions prior to 2026.2.26 fail to enforce sender authorization in member and message subtype system event handlers, allowing unauthorized events to be enqueued. Attackers can bypass Slack DM allowlists and per-channel user allowlists by sending system events from non-allowlisted senders through message_changed, message_deleted, and thread_broadcast events.

AnalysisAI

OpenClaw versions prior to 2026.2.26 contain an authentication bypass vulnerability in their Slack system event handlers that fails to properly enforce sender authorization checks. Attackers with low-privilege access (PR:L in CVSS vector) can craft and send unauthorized system events through message_changed, message_deleted, and thread_broadcast event types to bypass Slack DM allowlists and per-channel user allowlists. The vulnerability has a moderate CVSS score of 5.4 with low confidentiality and integrity impact; no KEV or active exploitation has been publicly disclosed, but a patch is available from the vendor.

Technical ContextAI

OpenClaw is a Slack integration platform (identified via CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) that processes Slack system events through member and message subtype handlers. The root cause is classified under CWE-863 (Incorrect Authorization), where the application fails to validate that incoming system events originate from authorized senders before enqueuing them for processing. The vulnerable code path accepts message_changed, message_deleted, and thread_broadcast events without performing sender identity verification, allowing attackers to spoof event sources and bypass downstream authorization checks that rely on per-channel or per-user allowlists. This represents a classic case of incomplete input validation in event-driven architectures where implicit trust assumptions about event provenance are not cryptographically validated.

RemediationAI

Upgrade OpenClaw to version 2026.2.26 or later as detailed in the vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-v8cg-4474-49v8. The specific patch commit is available at https://github.com/openclaw/openclaw/commit/3d30ba18a2aba1e1b302e77ff33145c3b06c01c8 for verification. If immediate patching is not feasible, consider temporarily disabling OpenClaw's processing of message_changed, message_deleted, and thread_broadcast events, or restricting OpenClaw's Slack bot token permissions to read-only access until the upgrade can be applied. Additionally, review Slack allowlist configurations to ensure they are not the sole control layer for event authorization.