How severe is CVE-2026-53843?

No CVSS score has been assigned to CVE-2026-53843 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-53843?

CVE-2026-53843 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-53843?

Update openclaw to 2026.5.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-53843 is resolved across your whole dependency graph.

How do I detect CVE-2026-53843 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 CVE-2026-53843 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-53843 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-53843 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 CVE-2026-53843?

CVE-2026-53843 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th 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 CVE-2026-53843?

CVE-2026-53843 is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-53843 published, and has it been updated?

CVE-2026-53843 was published on June 16, 2026 and was last updated on August 17, 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

CVE-2026-53843 — openclaw

CVE-2026-53843 is a CWE-613 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.5.26 - Node Token Revocation Bypass via Pairing-Scoped Device Session

Also known asGHSA-q99w-vh6v-q3v7

Published

Jun 16, 2026

Updated

Aug 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 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 CVE-2026-53843.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% 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

3.2Mdownloads / week

Description

Summary

In affected releases, a surviving pairing-scoped session for a device could re-establish node token authority after that node token had been revoked. Revocation should require the device to lose that authority unless it is approved again through the normal pairing flow.

This issue affects token revocation and device-role containment. It does not allow unauthenticated device creation.

Affected configurations

This affects deployments where an already paired device keeps a same-device session with pairing-related scope after its node token is revoked.

Impact

A device that should have lost node WebSocket authority could regain it without renewed approval. That weakens revocation as an operator control and can keep node-level access alive longer than intended.

The impact is limited to devices that already had a legitimate pairing/session foothold.

Patched Versions

The first stable patched version is 2026.5.26.

Mitigations

Upgrade to [email protected] or later. If a node token was revoked on an older version, restart the gateway and remove/re-pair the affected device to ensure no stale session remains active.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.5.26`npm install openclaw@2026.5.26`

Affected Products

1 product · 3 configurations

Application

openclawopenclaw

< 2026.5.26

1 version

2026.5.26

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.5.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-53843 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Summary In affected releases, a surviving pairing-scoped session for a device could re-establish node token authority after that node token had been revoked. Revocation should require the device to lose that authority unless it is approved again through the normal pairing flow. This issue affects token revocation and device-role containment. It does not allow unauthenticated device creation. ### Affected configurations This affects deployments where an already paired device keeps a same-device session with pairing-related scope after its node token is revoked. ### Impact A device tha

O3 Security · Impact-Aware SCA

Is CVE-2026-53843 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works