dbcve.org
OpenclawApplication

CVE-2026-41361

HIGH · 7.1 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
OpenClaw before 2026.3.28 contains an SSRF guard bypass vulnerability that fails to block four IPv6 special-use ranges. Attackers can exploit this by crafting URLs targeting internal or non-routable IPv6 addresses to bypass SSRF protections.

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 · high confidence

OpenClaw before version 2026.3.28 contains an SSRF (Server-Side Request Forgery) guard bypass vulnerability. The application's SSRF protection mechanism fails to block four IPv6 special-use address ranges, allowing attackers to craft URLs using internal or non-routable IPv6 addresses to bypass SSRF protections and potentially access internal resources.

MitigationUpgrade to OpenClaw version 2026.3.28 or later, which implements proper blocking of IPv6 special-use address ranges in the SSRF guard.

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
OpenclawApplication
Affected:< 2026.3.28

CVSS 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
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenClaw installation and version
    Locate the OpenClaw application on your system and determine its installed version number. Consult your system's package manager, application metadata, or the application's about/info section.
    Affected if The installed version is earlier than 2026.3.28 (e.g., 2026.3.27, 2026.2.x, or older)
  2. Confirm the SSRF protection feature is in use
    Review your OpenClaw configuration or usage patterns to determine whether the application makes outbound HTTP requests where SSRF protection would apply (e.g., URL fetching, webhooks, proxy features).
    Affected if The SSRF guard feature is enabled or the application processes external URLs submitted by users or systems
  3. Verify IPv6 address handling in SSRF guard
    If accessible, inspect the SSRF protection implementation or configuration to confirm whether IPv6 special-use addresses are being validated. Compare against known IPv6 special-use ranges (documentation may list the four ranges: link-local, unique local, loopback, and documentation prefixes).
    Affected if The SSRF guard does not explicitly block all four IPv6 special-use address ranges or allows IPv6 addresses from non-routable ranges
  4. Test for SSRF bypass using IPv6 addresses
    If you have access to a testing environment, attempt to access an internal resource using an IPv6 special-use address (such as ::1, fe80::/10, fc00::/7, or 2001:db8::/32) through the application's URL-fetching functionality.
    Affected if Requests to IPv6 special-use addresses succeed when they should be blocked, indicating the guard is bypassed

You are affected if OpenClaw version is earlier than 2026.3.28 and the SSRF protection feature is in use without proper blocking of IPv6 special-use address ranges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.3.28 or later
Fixed in 2026.3.28
Interim mitigation

Upgrade to OpenClaw version 2026.3.28 or later, which implements proper blocking of IPv6 special-use address ranges in the SSRF guard.

Recommended fix High confidence

2026.3.28

  1. Upgrade Openclaw to version 2026.3.28 or later to receive the SSRF guard fix that blocks the four IPv6 special-use ranges
  2. After upgrading, verify that SSRF protections now correctly block requests to IPv6 special-use addresses such as ::1 (loopback), fc00::/7 (unique local), fe80::/10 (link-local), and ff00::/8 (multicast)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41361 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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