Before OpenClaw 2026.4.2, remote CDP discovery could return a trailing-dot localhost host such as localhost. and bypass OpenClaw's loopback-host normalization. That let a non-loopback remote CDP profile pivot the follow-up connection back onto localhost.
A hostile discovery response could retarget authenticated browser control toward a localhost-resolving endpoint on the OpenClaw host. This weakened the existing remote-CDP loopback protection and could expose localhost-backed browser state.
openclaw (npm)<= 2026.4.1>= 2026.4.22026.4.19c22d636697336a6b22b0ae24798d8b8325d7828 — normalize localhost absolute-form CDP hosts before loopback checksThe 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 @smaeljaish771 for reporting.
{
"nvd_published_at": null,
"severity": "MODERATE",
"github_reviewed_at": "2026-04-07T18:15:56Z",
"github_reviewed": true,
"cwe_ids": [
"CWE-20",
"CWE-639"
]
}