ACVEAgent configuration vulnerability registry

ACVE-2026-0421

OpenClaw Control UI PoC exfiltrates a gateway token

Part of campaign: OpenClaw Control UI exposure

In the wild

weaponised-poc · bounty, research

Description

What

CVE-2026-25253 has a public one-click RCE chain through the OpenClaw Control UI and gatewayUrl token handling. The cited exposure census reported many reachable instances, but the research did not find a confirmed victim for this specific CVE. The status is therefore weaponised-poc.

Which configuration is exposed

The exposed setup is OpenClaw below 2026.1.29 with a reachable Control UI. A public UI and a vulnerable gatewayUrl handling path combine the version and exposure conditions; an unexposed local UI is outside the configuration.

How ACVE detects it

ACVE matches harness id and version plus the discovered Control UI reachability feature. It does not send the PoC, retrieve tokens, or infer public reachability from a hostname. Missing reachability is possible.

Fix

Upgrade to 2026.1.29 or later, bind Control UI to loopback or an authenticated proxy, and rotate gateway tokens after any exposure. Review browser history and network logs for PoC-like requests.

Grounding needed

The GitHub PoC and NVD entry should be checked for the fixed version and exploit mechanics. Exposure counts are retained as telemetry and not promoted to an exploited-itw status.

This record is limited to the condition named in the public source: OpenClaw Control UI PoC exfiltrates a gateway token. A match is a review signal for that condition, not a claim that every installation, package, model, or host was compromised. Operators should preserve the resolved evidence and investigate adjacent credentials, network exposure, and execution history before closing the finding. The result should be retained with the lock snapshot used for the match so later review can distinguish configuration drift from a changed public record.

Configuration

and
  harness.id eq "openclaw"
  harness.version semverRange "<2026.1.29"
  features["controlUI.reachable"] eq true

Fix

Upgrade OpenClaw to 2026.1.29 or later and keep Control UI private.

  • Upgrade harness:openclaw to 2026.1.29. Use the fixed release.
  • Reconfigure features["controlUI.reachable"] to false. Remove public UI exposure.

Validation

No validation entries recorded.

Grounding

No grounding checks recorded.

References

No references recorded.

Report a problemValidate this advisoryDiscussJSONEdit on GitHub