vulnerability · openclaw
OpenClaw browser actions could bypass private-network navigation checks
Some browser interactions could navigate beyond the initial private-network check. An authenticated caller with browser evaluation capability could read content that direct navigation policy would block.
medium severityhigh confidencepatchedNo known exploitation
Quick answer
What defenders need to know
- What is it?
- Some browser interactions could navigate beyond the initial private-network check. An authenticated caller with browser evaluation capability could read content that direct navigation policy would block.
- Who is affected?
- openclaw < 2026.5.18
- What should defenders do?
- Upgrade OpenClaw to 2026.5.18 or later.
- Is a fix available?
- Yes. Upgrade to 2026.5.18.
01 / Response
What to do
- Upgrade OpenClaw to 2026.5.18 or later.
- Until patched, limit browser control to trusted operators and avoid untrusted pages in environments with sensitive private web services.
02 / Technical assessment
Evidence-backed analysis
This requires enabled browser control and an authenticated caller interacting with an untrusted page. It is a browser navigation-policy issue, not an authentication bypass. The source does not establish observed exploitation.
- Some browser interactions could navigate beyond the initial private-network check. An authenticated caller with browser evaluation capability could read content that direct navigation policy would block.
03 / Timeline
Disclosure timeline
- GitHub Advisory Database publication
OpenClaw's browser act interactions could bypass private-network navigation checks
04 / Standards crosswalk
Standards crosswalk
No standards mappings are published for this record.
05 / Primary sources