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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 registration record (including a hashed credential and instanceid) was traversable by other local users. 2. 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…

Published by the source

6 May 2026, 23:23 UTC

Last modified by the source

6 May 2026, 23:36 UTC

Source last checked

26 Oct 2026, 12:51 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cqmh-pcgr-q42f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cqmh-pcgr-q42f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-cqmh-pcgr-q42f

Advisory: @axonflow/openclaw fix introduces plugin cache and credential-file permission hardening
IDs: GHSA-cqmh-pcgr-q42f
Record: https://patchnext.com/advisories/ghsa-cqmh-pcgr-q42f (revision 2, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @axonflow/openclaw 2.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @axonflow/openclaw: affected < 2.0.0; fixed in 2.0.0

## Suggested inspection (read-only)
- `npm ls @axonflow/openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @axonflow/openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cqmh-pcgr-q42f (OSV record GHSA-cqmh-pcgr-q42f lists affected ranges: npm @axonflow/openclaw >=0 <2.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-cqmh-pcgr-q42f (GitHub-reviewed advisory GHSA-cqmh-pcgr-q42f lists affected ranges: npm @axonflow/openclaw >=0 <2.0.0)

Commands are suggestions: review each one before running it.