PT-2026-25524 · Npm · Openclaw

Published 2026-03-04 · Updated 2026-03-04

OSV

CVSS v4.0

2.0

Low

Base vector

AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Summary

OpenClaw had account-scope gaps in pairing-store access for DM pairing policy, which could let a pairing approval from one account authorize the same sender on another account in multi-account setups.

Impact

This is an authorization-boundary weakness in multi-account channel deployments. A sender approved in one account could be accepted in another account before explicit approval there.

Affected Packages / Versions

• Package: openclaw (npm)
• Latest published version affected: 2026.2.25
• Vulnerable range: <= 2026.2.25
• Patched version (planned next release): >= 2026.2.26

Fix

OpenClaw now enforces account-scoped pairing reads/writes consistently across core and extension message channels, with stricter runtime/SDK helpers and shared policy wiring to prevent cross-account pairing bleed.

Fix Commit(s)

• a0c5e28f3bf0cc0cd9311f9e9ec2ca0352550dcf
• bce643a0bd145d3e9cb55400af33bd1b85baeb02

Release Process Note

patched versions is pre-set to the planned next release (2026.2.26). After npm publish of that version, this advisory is ready to publish without further content edits.

OpenClaw thanks @tdjackey for reporting.

Fix

Incorrect Authorization

Weakness Enumeration

CWE-863

Related Identifiers

GHSA-VJP8-WPRM-2JW9

Affected Products

Openclaw

References · 7

• https://osv.dev/vulnerability/GHSA-vjp8-wprm-2jw9 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2026-32067 · Security Note
• https://github.com/openclaw/openclaw · Note
• https://github.com/openclaw/openclaw/commit/bce643a0bd145d3e9cb55400af33bd1b85baeb02 · Note
• https://github.com/openclaw/openclaw/commit/a0c5e28f3bf0cc0cd9311f9e9ec2ca0352550dcf · Note
• https://github.com/openclaw/openclaw/security/advisories/GHSA-vjp8-wprm-2jw9 · Note
• https://vulncheck.com/advisories/openclaw-cross-account-authorization-bypass-in-dm-pairing-store · Note