{"answers":{"affected":"2 open source packages ship an affected version, including @axonflow/openclaw.","exploited":"There is no known exploitation of GHSA-cqmh-pcgr-q42f in the wild and no public exploit code.","fix":"Upgrade @axonflow/openclaw to 2.0.0 or later.","what":"GHSA-cqmh-pcgr-q42f is a vulnerability in @axonflow/openclaw, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-cqmh-pcgr-q42f and fix it if it is affected.\n\nWhat it is: GHSA-cqmh-pcgr-q42f is a vulnerability in @axonflow/openclaw, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-cqmh-pcgr-q42f in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @axonflow/openclaw (npm): affected all versions; fixed in 2.0.0\n- @axonflow/openclaw (npm): affected all versions; fixed in 2.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-cqmh-pcgr-q42f/ (Markdown: https://insights.sbomify.com/GHSA-cqmh-pcgr-q42f/index.md)","id":"GHSA-cqmh-pcgr-q42f","markdown":"https://insights.sbomify.com/GHSA-cqmh-pcgr-q42f/index.md","name":"GHSA-cqmh-pcgr-q42f","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AxonFlow npm plugin","requires_auth":"none","summary":"Local attackers can read registration credentials and cache data due to insecure file permissions in the AxonFlow plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## Summary\n\nTwo 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.\n\n## Affected versions\n\nVersions 1.3.2 and below.\n\n## Impact\n\n1. **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.\n2. **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.\n\nThe 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.\n\n## Remediation\n\nUpgrade 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.\n\n## Credit\n\nIdentified by AxonFlow internal security review.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"@axonflow/openclaw fix introduces plugin cache and credential-file permission hardening","id":"GHSA-cqmh-pcgr-q42f","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"@axonflow/openclaw","purl":null,"source":"GHSA-cqmh-pcgr-q42f"},{"ecosystem":"npm","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"@axonflow/openclaw","purl":"pkg:npm/%40axonflow/openclaw","source":"GHSA-cqmh-pcgr-q42f"}],"products":null,"published":"2026-05-06","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Local attackers can read registration credentials and cache data due to insecure file permissions in the AxonFlow plugin.","url":"https://insights.sbomify.com/GHSA-cqmh-pcgr-q42f/"}