How severe is GHSA-g375-h3v6-4873?

No CVSS score has been assigned to GHSA-g375-h3v6-4873 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g375-h3v6-4873?

GHSA-g375-h3v6-4873 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-g375-h3v6-4873?

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

How do I detect GHSA-g375-h3v6-4873 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-g375-h3v6-4873 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-g375-h3v6-4873?

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

Is GHSA-g375-h3v6-4873 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g375-h3v6-4873 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-g375-h3v6-4873?

GHSA-g375-h3v6-4873 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-g375-h3v6-4873?

GHSA-g375-h3v6-4873 is classified as CWE-184 (CWE-184). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g375-h3v6-4873 published, and has it been updated?

GHSA-g375-h3v6-4873 was published on April 17, 2026 and was last updated on July 8, 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-g375-h3v6-4873 — openclaw

Fix: openclaw/openclaw#64376

GHSA-g375-h3v6-4873 is a CWE-184 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Heartbeat owner downgrade missed local async exec completion events

Also known asCVE-2026-43578

Published

Apr 17, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-g375-h3v6-4873.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% 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

Heartbeat owner downgrade missed local async exec completion events.

Affected Packages / Versions

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

Impact

Local background exec completion text could be missed by heartbeat owner-downgrade detection, leaving a run in a more privileged context than intended after untrusted completion content.

Technical Details

The fix expands exec-completion detection to local background exec formats and adds targeted tests.

Fix

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

Fix Commit(s)

19a2e9ddb5a8a494abcba812bb11f51075026a27
PR: #64376

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 @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.3.31&&< 2026.4.10	2026.4.10`npm install openclaw@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g375-h3v6-4873 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-g375-h3v6-4873 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

## Summary Heartbeat owner downgrade missed local async exec completion events. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.3.31 < 2026.4.10` - Patched versions: `>= 2026.4.10` ## Impact Local background exec completion text could be missed by heartbeat owner-downgrade detection, leaving a run in a more privileged context than intended after untrusted completion content. ## Technical Details The fix expands exec-completion detection to local background exec formats and adds targeted tests. ## Fix The issue was fixed in #64376. T

O3 Security · Impact-Aware SCA

Is GHSA-g375-h3v6-4873 in your dependencies?

O3 Security finds GHSA-g375-h3v6-4873 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