GHSA-7FF8-XJH3-MGH6

GHSA-7FF8-XJH3-MGH6 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.22-2. It is fixed in 2026.2.23.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

OpenClaw's non-default autoAllowSkills setting could bypass on-miss exec prompt

In openclaw versions up to and including 2026.2.22-2, a non-default exec-approval configuration could allow a skill-name collision to bypass an ask=on-miss prompt.

When autoAllowSkills=true, a path-scoped executable such as ./skill-bin could resolve to basename skill-bin, satisfy the skills allowlist segment, and run without prompting for approval.

Affected Packages / Versions

  • Package: npm openclaw
  • Affected versions: <= 2026.2.22-2
  • Patched versions: >= 2026.2.23 (released)

Configuration Scope (Not Default)

This behavior requires non-default settings and does not affect default installs.

Required conditions:

  • autoAllowSkills=true (default is false)
  • system.run with security=allowlist
  • ask=on-miss

Technical Details

The allowlist evaluator accepted skills satisfaction by bin-name match, so ./skill-bin could match skillBins.has("skill-bin") after resolution.

The fix hardens skill auto-allow matching by requiring:

  • a pathless invocation token (no / or \\), and
  • a trusted resolved executable path for that skill bin on the machine where skills run.

This preserves normal skill-bin ... behavior while preventing ./<skill-bin> and absolute-path basename collisions from auto-satisfying skills.

Fix Commit(s)

  • ffd63b7a2c4c6d5aeb4710ef951d5794ad7ad77b (fix(security): trust resolved skill-bin paths in allowlist auto-allow)

OpenClaw thanks @tdjackey for reporting.

Impact

In affected non-default configurations, approval prompts could be skipped for commands that should have required operator confirmation.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Affected versions

openclaw (<= 2026.2.22-2)

Security releases

openclaw → 2026.2.23 (npm)

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.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade openclaw to 2026.2.23 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-7FF8-XJH3-MGH6? GHSA-7FF8-XJH3-MGH6 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.22-2. It is fixed in 2026.2.23. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
  2. Which versions of openclaw are affected by GHSA-7FF8-XJH3-MGH6? openclaw (npm) versions <= 2026.2.22-2 is affected.
  3. Is there a fix for GHSA-7FF8-XJH3-MGH6? Yes. GHSA-7FF8-XJH3-MGH6 is fixed in 2026.2.23. Upgrade to this version or later.
  4. Is GHSA-7FF8-XJH3-MGH6 exploitable, and should I be worried? Whether GHSA-7FF8-XJH3-MGH6 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
  5. What actually determines whether GHSA-7FF8-XJH3-MGH6 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.
  6. How do I fix GHSA-7FF8-XJH3-MGH6? Upgrade openclaw to 2026.2.23 or later.

Other vulnerabilities in openclaw

Stop the waste.
Protect your environment with Kodem.