Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-v6x2-2qvm-6gv8

LowCVSS 2.1 / 10
Published Mar 3, 2026·Last modified Mar 24, 2026
Affected Components(0)

No affected components available

Description

Vulnerability

OpenClaw reused gateway.auth.token (and gateway.remote.token) as a fallback hash secret for owner-ID prompt obfuscation when commands.ownerDisplay=hash and commands.ownerDisplaySecret was unset.

This created secret dual-use between gateway authentication and prompt metadata hashing.

Impact

  • Auth-secret dual-use across security domains (gateway auth and prompt metadata hashing).
  • Hash outputs are visible to third-party model providers in system prompts.
  • No direct plaintext token disclosure.
  • Practical risk is highest when operators use weak gateway tokens and leave owner hash secret unset.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest affected published version: 2026.2.21-2
  • Vulnerable range: <= 2026.2.21-2
  • Patched version (planned next release): 2026.2.22

Affected Components

  • src/agents/cli-runner/helpers.ts
  • src/agents/pi-embedded-runner/run/attempt.ts
  • src/agents/pi-embedded-runner/compact.ts

Remediation

  • Added a shared owner-display resolver and secret-generation helper.
  • Removed fallback to gateway.auth.token and gateway.remote.token.
  • Auto-generates and persists a dedicated commands.ownerDisplaySecret when hash mode is enabled and secret is missing.

Fix Commit(s)

  • c99e7696e6893083b256f0a6c88fb060f3a76fb7

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.22). Once npm release 2026.2.22 is published, this advisory only needs to be published.

OpenClaw thanks @aether-ai-agent for reporting.

Risk Scores
Base Score
2.1

The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
0.5

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.26%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Low severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard