Browser SSRF hostname validation could be bypassed by DNS rebinding.
openclaw< 2026.4.10>= 2026.4.10Browser navigation policy could validate a hostname/IP resolution that differed from the address Chromium ultimately used, allowing DNS rebinding style SSRF pivots.
The fix tightens strict browser hostname navigation so unallowlisted hostname URLs fail closed under restrictive policy.
The issue was fixed in #64367. The first stable tag containing the fix is v2026.4.10, and openclaw@2026.4.14 includes the fix.
121c452d666d4749744dc2089287d0227aae2ed3Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.
Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.
{
"github_reviewed_at": "2026-04-17T21:58:01Z",
"nvd_published_at": null,
"cwe_ids": [
"CWE-350",
"CWE-918"
],
"severity": "MODERATE",
"github_reviewed": true
}