OpenClaw accepted camera.snap / camera.clip node payload url fields and downloaded them on the gateway/agent host without binding downloads to the resolved node host.
In OpenClaw's documented trust model, paired nodes are in the same operator trust boundary, so this is scoped as medium-severity hardening. A malicious or compromised paired node could still steer gateway-host fetches during camera URL retrieval.
openclaw (npm)>= 2026.2.13 <= 2026.3.12026.3.1>= 2026.3.2 (released)Vulnerable flows accepted URL payloads and downloaded directly from the provided URL:
src/cli/nodes-camera.ts (writeUrlToFile) fetched URL payloads without node-host binding.src/cli/nodes-cli/register.camera.ts passed camera.snap / camera.clip payload URLs into that downloader.src/agents/tools/nodes-tool.ts did the same for camera_snap / camera_clip tool actions.A malicious/compromised paired node could cause gateway-host URL fetches to off-node destinations reachable from the host network. This could be used for internal network probing/fetch pivots in deployments where paired nodes are not fully trusted.
The fix introduces fail-closed node-host binding and guarded fetch for camera URL payload downloads:
3bf19d6f40a0aaa55818b96eede3d05130c02533{
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T21:18:56Z",
"nvd_published_at": null,
"severity": "MODERATE"
}