How severe is GHSA-x3h8-jrgh-p8jx?

No CVSS score has been assigned to GHSA-x3h8-jrgh-p8jx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x3h8-jrgh-p8jx?

GHSA-x3h8-jrgh-p8jx affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-x3h8-jrgh-p8jx?

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

How do I detect GHSA-x3h8-jrgh-p8jx 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-x3h8-jrgh-p8jx 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.

Is GHSA-x3h8-jrgh-p8jx actively exploited in the wild?

No public exploit code has been indexed for GHSA-x3h8-jrgh-p8jx 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-x3h8-jrgh-p8jx?

GHSA-x3h8-jrgh-p8jx has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-x3h8-jrgh-p8jx?

GHSA-x3h8-jrgh-p8jx 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-x3h8-jrgh-p8jx published, and has it been updated?

GHSA-x3h8-jrgh-p8jx was published on May 4, 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

OpenClaw's exec allowlist analysis rejects shell expansion in unquoted heredocsGHSA-x3h8-jrgh-p8jx

Fix: openclaw/openclaw@b2e8b7d

GHSA-x3h8-jrgh-p8jx is a CWE-184 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-44115

Published

May 4, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-x3h8-jrgh-p8jx.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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

Exec allowlist analysis rejects shell expansion in unquoted heredocs

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.4.21
Fixed version: 2026.4.22

Impact

An allowlisted command containing an unquoted heredoc could hide shell expansion in the heredoc body. That could make the approved command text look safer than what the shell would evaluate at runtime.

Fix

The exec command analyzer now tracks heredoc bodies, rejects unquoted heredoc expansion tokens and continuation-splice bypasses, and preserves quoted heredocs and literal safe text.

Fix Commit(s)

b2e8b7d4bb2f22eaa16f5c4b07547774e90b65a5

Verification

The fix commit is contained in the public v2026.4.22 tag.
[email protected] is published on npm and the compiled package contains the fix.
Focused regression coverage for this path passed before publication.

Thanks @VladimirEliTokarev for reporting.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.4.22

range

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.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3h8-jrgh-p8jx 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.

Frequently Asked Questions

## Summary Exec allowlist analysis rejects shell expansion in unquoted heredocs ## Affected Packages / Versions - Package: openclaw (npm) - Affected versions: <= 2026.4.21 - Fixed version: 2026.4.22 ## Impact An allowlisted command containing an unquoted heredoc could hide shell expansion in the heredoc body. That could make the approved command text look safer than what the shell would evaluate at runtime. ## Fix The exec command analyzer now tracks heredoc bodies, rejects unquoted heredoc expansion tokens and continuation-splice bypasses, and preserves quoted heredocs and literal safe te

O3 Security · Impact-Aware SCA

Is GHSA-x3h8-jrgh-p8jx in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works