GHSA-pjvx-rx66-r3fg — medium GitHub Advisory in npm/openclaw

Description

Summary

/allowlist ... --store resolved the selected channel accountId for reads, but store writes still dropped that accountId and wrote into the legacy unscoped pairing allowlist store.

Because default-account reads still merge legacy unscoped entries, a store entry intended for one account could silently authorize the same sender on the default account.

This is a real cross-account sender-authorization scoping bug. Severity is set to medium because exploitation requires an already-authorized user who can run /allowlist edits.

Affected Packages / Versions

Package: openclaw (npm)
Latest published version checked: 2026.3.2
Affected versions: <= 2026.3.2
Fixed on main: March 7, 2026 in 70da80bcb5574a10925469048d2ebb2abf882e73
Patched release: 2026.3.7

Details

The affected path was:
- src/auto-reply/reply/commands-allowlist.ts:386-393 resolved accountId and read store state with it
- src/auto-reply/reply/commands-allowlist.ts:697-702 and src/auto-reply/reply/commands-allowlist.ts:730-733 wrote store state without passing accountId
- src/pairing/pairing-store.ts:231-234 and src/pairing/pairing-store.ts:534-554 still merged legacy unscoped allowlist entries into the default account

The fix scopes /allowlist ... --store writes to the resolved account and clears legacy default-account store entries on removal so legacy reads no longer create cross-account authorization bleed-through.

Impact

Vulnerability class: improper authorization scoping / incorrect authorization
Exploitation requires: an already-authorized sender who can run /allowlist edits
Security effect: unintended authorization expansion from one channel account into default

Fix Commit(s)

70da80bcb5574a10925469048d2ebb2abf882e73 — scope /allowlist ... --store writes by account and clean up legacy default-account removals

Release Process Note

npm 2026.3.7 was published on March 8, 2026. This advisory is fixed in the released package.

Thanks @tdjackey for reporting.

Basic information

Type: reviewed
Severity: medium
Advisory on GitHub: Open advisory ↗
Repository advisory: Open repository advisory ↗
Source code: Browse source ↗
Published (advisory): 2026-03-09 19:54:08 UTC
Updated: 2026-03-09 19:54:09 UTC
GitHub reviewed: 2026-03-09 19:54:08 UTC

CVSS Scores

Base score	Version	Severity	Vector
5.4	3.1	—	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.

Identifiers

Type	Value
GHSA	GHSA-pjvx-rx66-r3fg ↗

CWEs

CWE id	Name
CWE-639	Authorization Bypass Through User-Controlled Key
CWE-863	Incorrect Authorization

Credits

tdjackey (reporter)

Affected packages (1)

Vulnerable version ranges and first patched releases as published by GitHub.

Ecosystem	Package	Vulnerable range	First patched	Vulnerable functions
npm	openclaw	<= 2026.3.2	2026.3.7	—

OpenClaw: Cross-account sender authorization expansion in `/allowlist ... --store` account scoping