How severe is GHSA-57r2-h2wj-g887?

No CVSS score has been assigned to GHSA-57r2-h2wj-g887 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-57r2-h2wj-g887?

GHSA-57r2-h2wj-g887 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-57r2-h2wj-g887?

Update openclaw to 2026.4.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-57r2-h2wj-g887 is resolved across your whole dependency graph.

How do I detect GHSA-57r2-h2wj-g887 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-57r2-h2wj-g887 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-57r2-h2wj-g887?

O3 pinpoints whether GHSA-57r2-h2wj-g887 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-57r2-h2wj-g887 actively exploited in the wild?

No public exploit code has been indexed for GHSA-57r2-h2wj-g887 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-57r2-h2wj-g887 published, and has it been updated?

GHSA-57r2-h2wj-g887 was published on April 25, 2026 and was last updated on May 19, 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-57r2-h2wj-g887

Fix: openclaw/openclaw@f61896b

GHSA-57r2-h2wj-g887 is a security vulnerability in openclaw. O3 Security confirms whether GHSA-57r2-h2wj-g887 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Isolated cron awareness events were recorded as trusted system events

Also known asCVE-2026-44999

Published

Apr 25, 2026

Updated

May 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: < 2026.4.20
Patched version: 2026.4.20

Impact

Output from webhook-triggered isolated cron agent runs could be queued into the main session awareness stream without trusted: false. That made the event render as a trusted System: event instead of an untrusted system event.

This is a trust-labeling issue that can strengthen prompt-injection impact, but it does not directly bypass gateway auth, tool policy, or sandboxing. Severity is low.

Fix

OpenClaw now preserves untrusted labels for isolated cron awareness events and forwards the trust flag through cron delivery helpers.

Fix commit:

f61896b03cc7031f51106a04566831f4ac2a0bd7

Release

Fixed in OpenClaw 2026.4.20.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.4.20

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.4.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-57r2-h2wj-g887 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-57r2-h2wj-g887 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-57r2-h2wj-g887. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `< 2026.4.20` - Patched version: `2026.4.20` ## Impact Output from webhook-triggered isolated cron agent runs could be queued into the main session awareness stream without `trusted: false`. That made the event render as a trusted `System:` event instead of an untrusted system event. This is a trust-labeling issue that can strengthen prompt-injection impact, but it does not directly bypass gateway auth, tool policy, or sandboxing. Severity is low. ## Fix OpenClaw now preserves untrusted labels for isolated c

O3 Security · Impact-Aware SCA

Is GHSA-57r2-h2wj-g887 in your dependencies?

O3 detects GHSA-57r2-h2wj-g887 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