How severe is GHSA-792q-qw95-f446?

No CVSS score has been assigned to GHSA-792q-qw95-f446 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-792q-qw95-f446?

GHSA-792q-qw95-f446 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-792q-qw95-f446?

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

How do I detect GHSA-792q-qw95-f446 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-792q-qw95-f446 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-792q-qw95-f446?

O3 pinpoints whether GHSA-792q-qw95-f446 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-792q-qw95-f446 actively exploited in the wild?

No public exploit code has been indexed for GHSA-792q-qw95-f446 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.

What is the EPSS score for GHSA-792q-qw95-f446?

GHSA-792q-qw95-f446 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-792q-qw95-f446?

GHSA-792q-qw95-f446 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-792q-qw95-f446 published, and has it been updated?

GHSA-792q-qw95-f446 was published on March 3, 2026 and was last updated on March 30, 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

GHSA-792q-qw95-f446

OpenClaw's Signal reaction-only status events could, in limited cases, be enqueued before access checks

Also known asCVE-2026-32050

Published

Mar 3, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk11th percentile+0.17%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.4Mdownloads / week

Description

Summary

In a narrow Signal reaction-notification path, reaction-only inbound events could enqueue a status event before sender access checks were applied.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.24 (latest published at patch time)
Fixed: 2026.2.25

Details

In the affected flow (src/signal/monitor/event-handler.ts), reaction-only handling could return after enqueueSystemEvent(...) before DM/group authorization checks were evaluated for that sender.

This behavior was limited to reaction-only inbound events with reaction notifications enabled. In that case, a sender not authorized for normal DM flow could still queue a Signal reaction status line for that session.

The fix applies shared DM/group access checks before reaction notification enqueue. Pairing behavior for normal DM messages is unchanged.

Impact

Limited to Signal reaction-only inbound events.
Could add an unauthorized reaction status line to agent context for affected sessions.
Did not directly enable normal DM delivery or direct host command execution.

Fix Commit(s)

2aa7842adeedef423be7ce283a9144b9f1a0a669

Release Process Note

patched_versions is pre-set to 2026.2.25 so once npm release is out, advisory publish can proceed directly.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-792q-qw95-f446 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 pinpoints whether GHSA-792q-qw95-f446 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-792q-qw95-f446. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary In a narrow Signal reaction-notification path, reaction-only inbound events could enqueue a status event before sender access checks were applied. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.24` (latest published at patch time) - Fixed: `2026.2.25` ### Details In the affected flow (`src/signal/monitor/event-handler.ts`), reaction-only handling could return after `enqueueSystemEvent(...)` before DM/group authorization checks were evaluated for that sender. This behavior was limited to reaction-only inbound events with reaction notification

O3 Security · Impact-Aware SCA

Is GHSA-792q-qw95-f446 in your dependencies?

O3 detects GHSA-792q-qw95-f446 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works