How severe is GHSA-qj22-xqjr-v83v?

No CVSS score has been assigned to GHSA-qj22-xqjr-v83v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qj22-xqjr-v83v?

GHSA-qj22-xqjr-v83v affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-qj22-xqjr-v83v?

Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qj22-xqjr-v83v is resolved across your whole dependency graph.

How do I detect GHSA-qj22-xqjr-v83v in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qj22-xqjr-v83v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qj22-xqjr-v83v?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qj22-xqjr-v83v can be triaged on real exposure rather than presence alone.

Is GHSA-qj22-xqjr-v83v actively exploited in the wild?

No public exploit code has been indexed for GHSA-qj22-xqjr-v83v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qj22-xqjr-v83v published, and has it been updated?

GHSA-qj22-xqjr-v83v was published on March 3, 2026 and was last updated on March 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-qj22-xqjr-v83v — openclaw

Fix: openclaw/openclaw@e56b0cf

GHSA-qj22-xqjr-v83v is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw's Telegram message_reaction authorization bypass allows unauthorized system-event injection

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.0Mdownloads / week

Description

A missing sender-authorization check in Telegram message_reaction handling allowed unauthorized users to trigger reaction-derived system events.

Affected Packages / Versions

Package: openclaw (npm)
Introduced: 2026.2.17
Affected: >= 2026.2.17 and <= 2026.2.24
Latest published at patch time: 2026.2.24
Patched in release: 2026.2.25

Impact

When reaction notifications are enabled, unauthorized Telegram senders could inject reaction system events despite configured DM/group authorization controls (dmPolicy, allowFrom, groupPolicy, groupAllowFrom).

Fix Commit(s)

e56b0cf1a04f992ac6ebc775899f48ea31687640

Release Process Note

patched_versions is pre-set to the release (2026.2.25) so once npm release 2026.2.25 is published, this advisory can be published without further edits.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.25`npm install openclaw@2026.2.25`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qj22-xqjr-v83v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qj22-xqjr-v83v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qj22-xqjr-v83v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A missing sender-authorization check in Telegram `message_reaction` handling allowed unauthorized users to trigger reaction-derived system events. ## Affected Packages / Versions - Package: `openclaw` (npm) - Introduced: `2026.2.17` - Affected: `>= 2026.2.17` and `<= 2026.2.24` - Latest published at patch time: `2026.2.24` - Patched in release: `2026.2.25` ## Impact When reaction notifications are enabled, unauthorized Telegram senders could inject reaction system events despite configured DM/group authorization controls (`dmPolicy`, `allowFrom`, `groupPolicy`, `groupAllowFrom`). ## Fix C

O3 Security · Impact-Aware SCA

Is GHSA-qj22-xqjr-v83v in your dependencies?

O3 Security finds GHSA-qj22-xqjr-v83v across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works