dbcve.org
OpenclawApplication

CVE-2026-31989

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-19
Fix available
A fix is available. Upgrade to 2026.3.1 or later.
See remediation →
69/100
Remediation priority · Elevated
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 versions prior to 2026.3.1 contain a server-side request forgery vulnerability in web_search citation redirect resolution that uses a private-network-allowing SSRF policy. An attacker who can influence citation redirect targets can trigger internal-network requests from the OpenClaw host to loopback, private, or internal destinations.

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 confidence

OpenClaw versions before 2026.3.1 contain an SSRF vulnerability in the web_search citation redirect resolution feature. The application uses a private-network-allowing SSRF policy, allowing attackers who control citation redirect targets to force the server to make requests to loopback (127.0.0.1), private (10.x, 192.168.x), or internal network destinations.

MitigationUpgrade to OpenClaw version 2026.3.1 or later. Additionally, implement strict SSRF protections by restricting allowed redirect targets to public endpoints and blocking requests to private/internal IP ranges.

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.1

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 installation and retrieve its version number (e.g., check the application binary, version file, or use --version flag)
    Affected if The installed version is before 2026.3.1 (any version < 2026.3.1)
  2. Determine if web_search citation feature is in use
    Inspect application configuration or logs to identify if the web_search citation redirect resolution feature is enabled or has been used
    Affected if The web_search citation redirect feature is active or configurable in the environment
  3. Review SSRF protection settings
    Examine the application's security configuration files or settings related to network request policies, specifically looking for rules governing redirect target validation
    Affected if The SSRF policy allows requests to private/internal IP ranges (127.0.0.1, 10.x, 192.168.x) or does not restrict redirect targets to public endpoints
  4. Test for SSRF vulnerability
    If you control a citation redirect target, configure it to point to an internal address (e.g., 127.0.0.1:port or 192.168.x.x) and observe if the server makes outbound requests to those internal destinations
    Affected if The application successfully makes requests to loopback or private network addresses when redirect targets point to those locations

A user is affected if OpenClaw version is before 2026.3.1 AND the web_search citation redirect feature is enabled AND the SSRF policy permits requests to private/internal network addresses.

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.1 or later
Fixed in 2026.3.1
Interim mitigation

Upgrade to OpenClaw version 2026.3.1 or later. Additionally, implement strict SSRF protections by restricting allowed redirect targets to public endpoints and blocking requests to private/internal IP ranges.

Recommended fix High confidence

2026.3.1

  1. 1. Identify the current OpenClaw version by checking the application or package manager
  2. 2. Review the web_search citation redirect configuration to understand current SSRF policy settings
  3. 3. Backup the current OpenClaw configuration and any associated data
  4. 4. Upgrade OpenClaw to version 2026.3.1 or later using the appropriate package manager or installation method
  5. 5. After upgrading, verify that the SSRF protection properly blocks requests to loopback (127.0.0.1, ::1), private (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), and internal network destinations
  6. 6. Test that legitimate web_search citation functionality still works as expected with the new SSRF restrictions
Caveat No breaking changes documented in provided material; minor version upgrade typically low risk

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31989 — 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-31989 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