How severe is GHSA-f934-5rqf-xx47?

No CVSS score has been assigned to GHSA-f934-5rqf-xx47 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f934-5rqf-xx47?

GHSA-f934-5rqf-xx47 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-f934-5rqf-xx47?

Update openclaw to 2026.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f934-5rqf-xx47 is resolved across your whole dependency graph.

How do I detect GHSA-f934-5rqf-xx47 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-f934-5rqf-xx47 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-f934-5rqf-xx47?

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

Is GHSA-f934-5rqf-xx47 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f934-5rqf-xx47 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-f934-5rqf-xx47?

GHSA-f934-5rqf-xx47 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th 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-f934-5rqf-xx47?

GHSA-f934-5rqf-xx47 is classified as CWE-183 (CWE-183). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f934-5rqf-xx47 published, and has it been updated?

GHSA-f934-5rqf-xx47 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-f934-5rqf-xx47 — openclaw

Fix: openclaw/openclaw#66026

GHSA-f934-5rqf-xx47 is a CWE-183 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: QMD memory_get restricts reads to canonical or indexed memory paths

Also known asCVE-2026-44111

Published

Apr 17, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 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-f934-5rqf-xx47.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

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

3.1Mdownloads / week

Description

Summary

The QMD backend memory_get read path accepted arbitrary workspace Markdown paths that were inside the workspace but outside the canonical memory locations or indexed QMD result set.

Impact

When the QMD backend was enabled, a caller with access to memory_get could read arbitrary *.md files under the configured workspace root, even when those files were not canonical memory files and had not been returned by QMD search. Severity remains low because exploitation requires access to the memory tool surface and is limited to workspace Markdown files, but it bypassed the intended memory-path policy.

Affected versions

Affected: < 2026.4.15
Patched: 2026.4.15

Fix

OpenClaw 2026.4.15 restricts QMD reads to canonical memory paths or previously indexed QMD workspace paths. Workspace containment alone is no longer sufficient.

Verified in v2026.4.15:

extensions/memory-core/src/memory/qmd-manager.ts rejects non-default workspace Markdown paths unless they match an indexed QMD workspace read path.
extensions/memory-core/src/memory/qmd-manager.test.ts covers QMD session search-result reads and the read-path restriction behavior.

Fix commit included in v2026.4.15 and absent from v2026.4.14:

37d5971db36491d5050efd42c333cbe0b98ed292 via PR #66026

Thanks to @zsxsoft, Keen Security Lab, and @qclawer for reporting this issue.

Affected Packages

1 total 1 fixed

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

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

Tailored to GHSA-f934-5rqf-xx47. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The QMD backend `memory_get` read path accepted arbitrary workspace Markdown paths that were inside the workspace but outside the canonical memory locations or indexed QMD result set. ## Impact When the QMD backend was enabled, a caller with access to `memory_get` could read arbitrary `*.md` files under the configured workspace root, even when those files were not canonical memory files and had not been returned by QMD search. Severity remains low because exploitation requires access to the memory tool surface and is limited to workspace Markdown files, but it bypassed the intend

O3 Security · Impact-Aware SCA

Is GHSA-f934-5rqf-xx47 in your dependencies?

O3 Security finds GHSA-f934-5rqf-xx47 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