Quick answers
- Is CVE-2026-35663 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35663 being exploited in the wild.
- How severe is CVE-2026-35663?
- Critical severity, with a CVSS score of 8.8, published 10 April 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,last_affected=2026.3.24; Openclaw <= 2026.3.24.
- Is there a fix for CVE-2026-35663?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-35663 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-35663?
- Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A privilege escalation vulnerability exists in OpenClaw due to improper authorization checks during backend-labeled reconnection. The system previously allowed reconnecting sessions to self-request broader scopes and bypass the pairing process if they were labeled as backend components. An attacker with low-privileged 'operator' access can exploit this by requesting the 'operator.admin' scope during a reconnect, effectively bypassing security baselines. The fix, implemented in commit d3d8e316bd819d3c7e34253aeb7eccb2510f5f48, removes the self-pairing skip and enforces pairing whenever requested scopes exceed the approved baseline.
Affected products
- OpenClaw openclaw <= 2026.3.24
Identifiers
- CVE-2026-35663
- GHSA-9hjh-fr4f-gxc4
Timeline
- 2026-03-26: disclosed
- 2026-03-27: advisory: GHSA-9hjh-fr4f-gxc4 published