How severe is GHSA-jfv4-h8mc-jcp8?

No CVSS score has been assigned to GHSA-jfv4-h8mc-jcp8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jfv4-h8mc-jcp8?

GHSA-jfv4-h8mc-jcp8 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jfv4-h8mc-jcp8?

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

How do I detect GHSA-jfv4-h8mc-jcp8 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-jfv4-h8mc-jcp8 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-jfv4-h8mc-jcp8?

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

Is GHSA-jfv4-h8mc-jcp8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jfv4-h8mc-jcp8 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-jfv4-h8mc-jcp8?

GHSA-jfv4-h8mc-jcp8 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th 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-jfv4-h8mc-jcp8?

GHSA-jfv4-h8mc-jcp8 is classified as CWE-283 (CWE-283). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jfv4-h8mc-jcp8 published, and has it been updated?

GHSA-jfv4-h8mc-jcp8 was published on February 18, 2026 and was last updated on February 23, 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-jfv4-h8mc-jcp8 — openclaw

Fix: openclaw/openclaw@6084d13

GHSA-jfv4-h8mc-jcp8 is a CWE-283 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Process Safety - Unvalidated PID Kill via SIGKILL in Process Cleanup

Also known asCVE-2026-27486

Published

Feb 18, 2026

Updated

Feb 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-jfv4-h8mc-jcp8.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

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.

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

2.5Mdownloads / week

Description

Summary

OpenClaw CLI process cleanup used system-wide process enumeration and pattern matching to terminate processes without verifying they were owned by the current OpenClaw process. On shared hosts, unrelated processes could be terminated if they matched the pattern.

Affected Packages / Versions

Package: openclaw (npm)
Affected: < 2026.2.14 (including the latest published version 2026.2.13)
Fixed: 2026.2.14 (planned next release)

Details

The CLI runner cleanup helpers could kill processes matched by command-line patterns without validating process ownership.

Fix

Process cleanup is now scoped to owned processes only by filtering to direct child PIDs of the current process (ppid == process.pid) before sending signals.

Hardening follow-ups:

Prefer graceful termination for resume cleanup (SIGTERM, then SIGKILL fallback).
Reduce false negatives from ps argv truncation by preferring wide output (ps -axww) with a fallback.
Tighten command-line token matching to avoid substring matches.

Fix Commit(s)

6084d13b956119e3cf95daaf9a1cae1670ea3557
eb60e2e1b213740c3c587a7ba4dbf10da620ca66

Release Process Note

This advisory is pre-set with patched version 2026.2.14. After 2026.2.14 is published to npm, the remaining step should be to publish this advisory.

Thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

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

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.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jfv4-h8mc-jcp8 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-jfv4-h8mc-jcp8 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

## Summary OpenClaw CLI process cleanup used system-wide process enumeration and pattern matching to terminate processes without verifying they were owned by the current OpenClaw process. On shared hosts, unrelated processes could be terminated if they matched the pattern. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `< 2026.2.14` (including the latest published version `2026.2.13`) - Fixed: `2026.2.14` (planned next release) ## Details The CLI runner cleanup helpers could kill processes matched by command-line patterns without validating process ownership. ##

O3 Security · Impact-Aware SCA

Is GHSA-jfv4-h8mc-jcp8 in your dependencies?

O3 Security finds GHSA-jfv4-h8mc-jcp8 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