How severe is GHSA-cqmh-pcgr-q42f?

GHSA-cqmh-pcgr-q42f has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cqmh-pcgr-q42f?

GHSA-cqmh-pcgr-q42f affects the following packages: @axonflow/openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-cqmh-pcgr-q42f?

Update @axonflow/openclaw to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqmh-pcgr-q42f is resolved across your whole dependency graph.

How do I detect GHSA-cqmh-pcgr-q42f in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @axonflow/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-cqmh-pcgr-q42f 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-cqmh-pcgr-q42f?

O3 pinpoints whether GHSA-cqmh-pcgr-q42f 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-cqmh-pcgr-q42f actively exploited in the wild?

No public exploit code has been indexed for GHSA-cqmh-pcgr-q42f 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-cqmh-pcgr-q42f published, and has it been updated?

GHSA-cqmh-pcgr-q42f was published on May 6, 2026 and was last updated on May 6, 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

GHSA-cqmh-pcgr-q42f

MEDIUM

@axonflow/openclaw fix introduces plugin cache and credential-file permission hardening

Published

May 6, 2026

Updated

May 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦@axonflow/openclaw

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Two related permission defects in this AxonFlow plugin allowed registration credentials and cache state to be readable by other local users on hosts where the calling user's home directory was at the conventional 0755 mode.

Affected versions

Versions 1.3.2 and below.

Impact

Cache and config directory mode. The plugin's directories under ~/.config/axonflow/ and ~/.cache/axonflow/ were created with the umask-derived default mode (often 0755) on first use and not subsequently re-validated. On systems where ~/.config/ is itself 0755, the plugin's registration record (including a hashed credential and instance_id) was traversable by other local users.
Credential file mode at load time. The plugin loaded its try-registration.json credential file without validating that the file mode was 0600. A registration file written by a misconfigured tool, copied across systems, or restored from backup could end up world-readable, and the plugin would silently use it.

The fix restores 0700 on all plugin directories on every plugin invocation (not only first creation) and refuses to load credential files with non-0600 modes.

Remediation

Upgrade to the patched plugin version listed under Vulnerabilities. On startup the plugin will repair existing directory modes; existing credential files with overly permissive modes will be refused, requiring the user to re-register or chmod 0600 the file.

Credit

Identified by AxonFlow internal security review.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@axonflow/openclaw`	all versions	2.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @axonflow/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 @axonflow/openclaw to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqmh-pcgr-q42f 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-cqmh-pcgr-q42f 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-cqmh-pcgr-q42f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Two related permission defects in this AxonFlow plugin allowed registration credentials and cache state to be readable by other local users on hosts where the calling user's home directory was at the conventional `0755` mode. ## Affected versions Versions 1.3.2 and below. ## Impact 1. **Cache and config directory mode.** The plugin's directories under `~/.config/axonflow/` and `~/.cache/axonflow/` were created with the umask-derived default mode (often `0755`) on first use and not subsequently re-validated. On systems where `~/.config/` is itself `0755`, the plugin's registrati

O3 Security · Impact-Aware SCA

Is GHSA-cqmh-pcgr-q42f in your dependencies?

O3 detects GHSA-cqmh-pcgr-q42f 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