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.
Credit
Identified by AxonFlow internal security review.
Impact
- Cache and config directory mode. The plugin's directories under
~/.config/axonflow/and~/.cache/axonflow/were created with the umask-derived default mode (often0755) on first use and not subsequently re-validated. On systems where~/.config/is itself0755, the plugin's registration record (including a hashed credential andinstance_id) was traversable by other local users. - Credential file mode at load time. The plugin loaded its
try-registration.jsoncredential file without validating that the file mode was0600. 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.
A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.
GHSA-CQMH-PCGR-Q42F has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is GHSA-CQMH-PCGR-Q42F? GHSA-CQMH-PCGR-Q42F is a medium-severity incorrect permission assignment for critical resource vulnerability in @axonflow/openclaw (npm), affecting versions < 2.0.0. It is fixed in 2.0.0. A file, directory, or other resource is assigned permissions that allow broader access than intended.
- How severe is GHSA-CQMH-PCGR-Q42F? GHSA-CQMH-PCGR-Q42F has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @axonflow/openclaw are affected by GHSA-CQMH-PCGR-Q42F? @axonflow/openclaw (npm) versions < 2.0.0 is affected.
- Is there a fix for GHSA-CQMH-PCGR-Q42F? Yes. GHSA-CQMH-PCGR-Q42F is fixed in 2.0.0. Upgrade to this version or later.
- Is GHSA-CQMH-PCGR-Q42F exploitable, and should I be worried? Whether GHSA-CQMH-PCGR-Q42F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-CQMH-PCGR-Q42F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-CQMH-PCGR-Q42F? Upgrade
@axonflow/openclawto 2.0.0 or later.