CVE-2026-35673
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw before 2026.4.29 contains an SSRF policy bypass vulnerability in browser debug and export routes that allows reuse of already-open blocked tabs. Attackers with access to these routes can bypass private-network SSRF policies by reusing blocked tabs to export or inspect content that should remain protected.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenClaw before 2026.4.29 has an SSRF policy bypass in its browser debug and export routes. Attackers with access to these routes can reuse already-open blocked tabs to bypass private-network SSRF protections, allowing them to export or inspect content that should be protected.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.4.29CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed OpenClaw versionLocate the OpenClaw application and check its version information, typically available in the application binary, about dialog, or version file included with the installationAffected if The installed version is lower than 2026.4.29
-
Identify if browser debug routes are exposedReview OpenClaw's web server or API configuration to determine if debug endpoints related to browser functionality are accessible or enabledAffected if Debug routes are enabled and accessible without additional restrictions
-
Identify if export routes are exposedReview OpenClaw's web server or API configuration to determine if export endpoints are accessible or enabledAffected if Export routes are enabled and accessible without additional restrictions
-
Check tab state management configurationInspect the application's configuration for any settings related to tab management, blocked tabs, or browser automation that controls how tabs are created, reused, or isolated during debug/export operationsAffected if The application allows reuse of previously blocked tabs across different operations or lacks proper tab isolation
A user is affected if their OpenClaw version is below 2026.4.29 AND they have debug or export routes enabled, particularly if tab reuse across these features is not explicitly prevented.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.4.29
Upgrade to OpenClaw version 2026.4.29 or later. Additionally, restrict access to debug and export routes and implement stricter network segmentation to limit SSRF attack surface.
2026.4.29
- 1. Identify all deployments of OpenClaw currently running versions prior to 2026.4.29
- 2. Review the OpenClaw release notes or changelog for version 2026.4.29 to confirm it contains the SSRF policy bypass fix
- 3. Schedule a maintenance window for the upgrade
- 4. Backup the OpenClaw configuration and any associated data
- 5. Upgrade OpenClaw to version 2026.4.29 or later following the standard upgrade procedure
- 6. Verify the upgrade was successful and the application is functioning correctly
- 7. Test that the browser debug and export routes properly enforce SSRF policies and cannot be bypassed via tab reuse
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35673 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data