GHSA-HV93-R4J3-Q65F

GHSA-HV93-R4J3-Q65F is a high-severity use of insufficiently random values vulnerability in openclaw (npm), affecting versions >= 2.0.0-beta3, < 2026.2.12. It is fixed in 2026.2.12.

Summary

The issue is not deterministic session keys by itself. The exploitable path was accepting externally supplied sessionKey values on authenticated hook ingress, allowing a hook token holder to route messages into chosen sessions.

Affected Behavior

  • POST /hooks/agent accepted payload sessionKey and used it directly for session routing.
  • Common session-key shapes (for example agent:main:dm:<peerId>) were often derivable from known metadata, making targeted routing practical when request-level override was enabled.

Attack Preconditions

  • Attacker can call hook endpoints with a valid hook token.
  • Hook ingress allows request-selected sessionKey values.
  • Target session keys can be derived or guessed.

Without those preconditions, deterministic key formats alone do not provide access.

Affected Versions

  • openclaw >= 2.0.0-beta3 and < 2026.2.12

Patched Versions

  • openclaw >= 2026.2.12

Recommended Configuration

{
  "hooks": {
    "enabled": true,
    "token": "${OPENCLAW_HOOKS_TOKEN}",
    "defaultSessionKey": "hook:ingress",
    "allowRequestSessionKey": false,
    "allowedSessionKeyPrefixes": ["hook:"]
  }
}

Credit

Thanks @alpernae for responsible reporting.

Impact

  • Integrity: targeted message/prompt injection into chosen sessions.
  • Persistence: poisoned context can affect subsequent turns when the same session key is reused.
  • Confidentiality impact is secondary and depends on additional weaknesses.

Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.

GHSA-HV93-R4J3-Q65F has a CVSS score of 7.1 (High). The vector is network-reachable, 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 (2026.2.12); upgrading removes the vulnerable code path.

Affected versions

openclaw (>= 2.0.0-beta3, < 2026.2.12)

Security releases

openclaw → 2026.2.12 (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.

See it in your environment

Remediation advice

OpenClaw now uses secure defaults for hook session routing:

  • POST /hooks/agent rejects payload sessionKey unless hooks.allowRequestSessionKey=true.
  • Added hooks.defaultSessionKey for fixed ingress routing.
  • Added hooks.allowedSessionKeyPrefixes to constrain explicit routing keys.
  • Security audit warns on unsafe hook session-routing settings.

Frequently Asked Questions

  1. What is GHSA-HV93-R4J3-Q65F? GHSA-HV93-R4J3-Q65F is a high-severity use of insufficiently random values vulnerability in openclaw (npm), affecting versions >= 2.0.0-beta3, < 2026.2.12. It is fixed in 2026.2.12. Security-sensitive operations rely on values that are predictable or insufficiently random.
  2. How severe is GHSA-HV93-R4J3-Q65F? GHSA-HV93-R4J3-Q65F has a CVSS score of 7.1 (High). 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.
  3. Which versions of openclaw are affected by GHSA-HV93-R4J3-Q65F? openclaw (npm) versions >= 2.0.0-beta3, < 2026.2.12 is affected.
  4. Is there a fix for GHSA-HV93-R4J3-Q65F? Yes. GHSA-HV93-R4J3-Q65F is fixed in 2026.2.12. Upgrade to this version or later.
  5. Is GHSA-HV93-R4J3-Q65F exploitable, and should I be worried? Whether GHSA-HV93-R4J3-Q65F 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
  6. What actually determines whether GHSA-HV93-R4J3-Q65F 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.
  7. How do I fix GHSA-HV93-R4J3-Q65F? Upgrade openclaw to 2026.2.12 or later.

Other vulnerabilities in openclaw

CVE-2026-53811CVE-2026-53816CVE-2026-53806CVE-2026-53818CVE-2026-53809

Stop the waste.
Protect your environment with Kodem.