LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32897: OpenClaw < 2026.2.22 - Authentication Token Reuse in Owner ID Prompt Hashing Fallback

OpenClaw versions prior to 2026.2.22 reuse gateway.auth.token as a fallback hash secret for owner-ID prompt obfuscation when commands.ownerDisplay is set to hash and commands.ownerDisplaySecret is unset, creating dual-use of authentication secrets across security domains. Attackers with access to system prompts sent to third-party model providers can derive the gateway authentication token from the hash outputs, compromising gateway authentication security.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OpenClaw could reuse its gateway authentication token for a separate owner-ID hashing feature. If prompts containing those hashes were sent to a third-party model provider, someone with access to those prompts might derive the gateway token and authenticate to the gateway.

Executive priority

Treat as a moderate-priority secret exposure issue. Prioritize internet-facing or third-party-model-connected OpenClaw deployments, because compromise of the gateway token could weaken authentication even though exploitation conditions appear narrow.

Technical view

Before 2026.2.22, OpenClaw falls back to gateway.auth.token as the hash secret when commands.ownerDisplay is hash and commands.ownerDisplaySecret is unset. This cross-domain secret reuse can expose the gateway authentication token through owner-ID prompt hash outputs. CVSS is 6.3 medium with high attack complexity and no public exploitation evidence in the bundle.

Likely exposure

Exposure appears limited to OpenClaw deployments before 2026.2.22 using hashed owner display without a dedicated ownerDisplaySecret, especially where prompts are shared with third-party model providers or retained in logs.

Exploitation context

The bundle does not show active exploitation, and KEV is false. Exploitation depends on access to system prompts or prompt logs containing relevant hash outputs and enough conditions to derive or misuse the reused gateway secret.

Researcher notes

The key condition is fallback secret selection, not the hash algorithm alone. Validate configuration state and prompt exposure paths. The provided sources do not prove exploit availability, mass scanning, or impact beyond gateway token compromise risk.

Mitigation direction

  • Upgrade OpenClaw to 2026.2.22 or later per vendor guidance.
  • Set a dedicated ownerDisplaySecret if using hashed owner display.
  • Do not reuse gateway.auth.token for unrelated hashing or obfuscation purposes.
  • Rotate gateway authentication tokens after remediation if prompts may have been exposed.
  • Review third-party model provider prompt retention and access controls.

Validation and detection

  • Identify OpenClaw versions older than 2026.2.22.
  • Check whether commands.ownerDisplay is set to hash.
  • Check whether commands.ownerDisplaySecret is unset in affected deployments.
  • Review prompt logs sent to third-party model providers for owner-ID hash exposure.
  • Confirm gateway.auth.token was rotated after any suspected exposure.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-320: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32897 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheck
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

6.3Medium
CVSS 4.0 vector shape for CVE-2026-32897Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenClawOpenClaw0, 2026.2.22unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-320 · source CWE mapping

Key Management Errors

Key Management Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.