Before OpenClaw 2026.4.2, POST /sessions/:sessionKey/kill did not enforce write scopes in identity-bearing HTTP modes. A caller limited to read-only operator scopes could still terminate a running subagent session.
A read-scoped caller could perform a write-class control-plane mutation and interrupt delegated work. This was an authorization bug on the HTTP scope boundary, not a shared-secret compatibility exception.
openclaw (npm)<= 2026.4.1>= 2026.4.22026.4.154a0878517167c6e49900498cf77420dadb74beb — enforce session-kill HTTP scopesThe fix is present on main and is staged for OpenClaw 2026.4.2. Publish this advisory after the 2026.4.2 npm release is live.
Thanks @EaEa0001 for reporting.
{
"github_reviewed": true,
"severity": "MODERATE",
"github_reviewed_at": "2026-04-07T18:15:37Z",
"nvd_published_at": "2026-04-21T00:16:30Z",
"cwe_ids": [
"CWE-269",
"CWE-862"
]
}