How severe is GHSA-553v-f69r-656j?

No CVSS score has been assigned to GHSA-553v-f69r-656j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-553v-f69r-656j?

GHSA-553v-f69r-656j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-553v-f69r-656j?

Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-553v-f69r-656j is resolved across your whole dependency graph.

How do I detect GHSA-553v-f69r-656j in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-553v-f69r-656j if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-553v-f69r-656j actively exploited in the wild?

No public exploit code has been indexed for GHSA-553v-f69r-656j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-553v-f69r-656j?

GHSA-553v-f69r-656j has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-553v-f69r-656j?

GHSA-553v-f69r-656j is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-553v-f69r-656j published, and has it been updated?

GHSA-553v-f69r-656j was published on March 3, 2026 and was last updated on April 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

OpenClaw unpaired device identity can bypass operator pairing and self-assign operator scopes with shared authGHSA-553v-f69r-656j

Fix: openclaw/openclaw@8d1481c

GHSA-553v-f69r-656j is a CWE-863 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-32042

Published

Mar 3, 2026

Updated

Apr 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-553v-f69r-656j.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.4Mdownloads / week

Description

Summary

A client using shared gateway auth could attach an unpaired device identity and request elevated operator scopes (including operator.admin) before pairing approval, enabling privilege escalation.

Impact

Attackers with valid shared gateway auth could self-assign higher operator scopes by presenting a self-signed, unpaired device identity.

Affected Packages / Versions

Package: openclaw (npm)
Affected: >= 2026.2.22 <= 2026.2.24
Latest published npm at triage time: 2026.2.24
Planned patched release: 2026.2.25

Remediation

Require pairing for operator device-identity sessions authenticated with shared token/password auth (except existing control-ui trusted-proxy/control-ui bypass policy paths).

Fix Commit(s)

8d1481cb4a9d31bd617e52dc8c392c35689d9dea

Release Process Note

patched_versions is pre-set to the release (>= 2026.2.25). Advisory published with npm release 2026.2.25.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.2.22&&< 2026.2.25	2026.2.25`npm install openclaw@2026.2.25`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

≥ 2026.2.22 && < 2026.2.25

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-553v-f69r-656j is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### Summary A client using shared gateway auth could attach an unpaired device identity and request elevated operator scopes (including `operator.admin`) before pairing approval, enabling privilege escalation. ### Impact Attackers with valid shared gateway auth could self-assign higher operator scopes by presenting a self-signed, unpaired device identity. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `>= 2026.2.22 <= 2026.2.24` - Latest published npm at triage time: `2026.2.24` - Planned patched release: `2026.2.25` ### Remediation Require pairing for operator dev

O3 Security · Impact-Aware SCA

Is GHSA-553v-f69r-656j in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works