dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-42260

HIGH · 8.2 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Open-WebSearch is a multi-engine MCP server, CLI, and local daemon for agent web search and content retrieval. Prior to 2.1.7, isPublicHttpUrl / assertPublicHttpUrl in src/utils/urlSafety.ts do not recognize bracketed IPv6 literals and do not resolve DNS, which combine to allow non-blind SSRF with the response body returned to the caller. This vulnerability is fixed in 2.1.7.

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

The isPublicHttpUrl and assertPublicHttpUrl functions in Open-WebSearch fail to validate bracketed IPv6 addresses and do not perform DNS resolution, allowing attackers to bypass URL validation and make the server request internal network resources. This enables non-blind SSRF where the attacker receives the response body from internal services.

MitigationUpgrade to Open-WebSearch version 2.1.7 or later, which includes proper IPv6 literal recognition and DNS resolution in the URL safety validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Open-WebSearch installation version
    Locate the Open-WebSearch installation directory and check the version file, package.json, or version metadata. Common locations: package.json for Node.js installations, or a VERSION file in the root directory. Run: cat package.json | grep version or ls -la for version files.
    Affected if The installed version is lower than 2.1.7 (any version prior to the fix is vulnerable)
  2. Locate the URL validation module
    Search for files containing 'isPublicHttpUrl' or 'assertPublicHttpUrl' functions in the codebase. Use grep: grep -r 'isPublicHttpUrl' . or grep -r 'assertPublicHttpUrl' .
    Affected if These functions exist in the codebase and are used for URL validation
  3. Identify URL-handling endpoints
    Review the application's HTTP routes or endpoints that accept URLs as input. Look for parameters named 'url', 'href', 'redirect', or similar that accept user-provided URLs. Check route handlers in main application files.
    Affected if The application accepts user-supplied URLs that are passed through the vulnerable validation functions
  4. Test for IPv6 address handling
    Submit a request with a bracketed IPv6 address pointing to an internal resource, such as http://[::1] or http://[fe80::1], as a URL parameter. Observe whether the server makes a request to the internal address.
    Affected if The server accepts bracketed IPv6 addresses and attempts to resolve/request them without proper validation

A user is affected if they run Open-WebSearch version lower than 2.1.7 and the application exposes endpoints that accept user URLs processed by the isPublicHttpUrl or assertPublicHttpUrl functions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Open-WebSearch version 2.1.7 or later, which includes proper IPv6 literal recognition and DNS resolution in the URL safety validation.

Recommended fix High confidence

2.1.7

  1. Upgrade Open-WebSearch to version 2.1.7 or later to obtain the patched version of src/utils/urlSafety.ts that properly validates bracketed IPv6 literals and resolves DNS for SSRF protection

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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