How severe is GHSA-jf25-7968-h2h5?

No CVSS score has been assigned to GHSA-jf25-7968-h2h5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jf25-7968-h2h5?

GHSA-jf25-7968-h2h5 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jf25-7968-h2h5?

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

How do I detect GHSA-jf25-7968-h2h5 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-jf25-7968-h2h5 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-jf25-7968-h2h5?

O3 pinpoints whether GHSA-jf25-7968-h2h5 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-jf25-7968-h2h5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jf25-7968-h2h5 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-jf25-7968-h2h5 published, and has it been updated?

GHSA-jf25-7968-h2h5 was published on April 17, 2026 and was last updated on May 5, 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-jf25-7968-h2h5

Fix: openclaw/openclaw#63551

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

OpenClaw: screen_record outPath bypassed workspace-only filesystem guard

Also known asCVE-2026-43567

Published

Apr 17, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 5, 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, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Summary

screen_record outPath bypassed workspace-only filesystem guard.

Affected Packages / Versions

Package: openclaw
Ecosystem: npm
Affected versions: < 2026.4.10
Patched versions: >= 2026.4.10

Impact

The node-host screen recording tool could honor an outPath outside the workspace guard, allowing an authorized tool call to write outside the intended workspace boundary.

Technical Details

The fix applies the workspace-root guard to node tool outPath handling, including screen recording paths.

Fix

The issue was fixed in #63551. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.

Fix Commit(s)

635bb35b68d8faa5bfa2fda35feadd315122748a
PR: #63551

Release Process Note

Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @anshumanbh for reporting this issue.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary screen_record outPath bypassed workspace-only filesystem guard. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `< 2026.4.10` - Patched versions: `>= 2026.4.10` ## Impact The node-host screen recording tool could honor an `outPath` outside the workspace guard, allowing an authorized tool call to write outside the intended workspace boundary. ## Technical Details The fix applies the workspace-root guard to node tool `outPath` handling, including screen recording paths. ## Fix The issue was fixed in #63551. The first stable tag cont

O3 Security · Impact-Aware SCA

Is GHSA-jf25-7968-h2h5 in your dependencies?

O3 detects GHSA-jf25-7968-h2h5 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