CVE-2026-42260: Aas-ee open-webSearch · Server-Side Request Forgery (SSRF)
Affects Aas-ee open-webSearchSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 2.1.7 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade open-webSearch and aas-ee/open-webSearch to 2.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Aas-eeopen-webSearch | Affected
| Fixed in
|
GitHubaas-ee/open-webSearchpkg:github/aas-ee/open-webSearchOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade open-webSearch to version 2.1.7 or later, where the vulnerability is fixed. Since the product is not a cloud service and no other remediation level is provided, applying this official fix is the recommended action. Patch status is confirmed by the vendor advisory stating the issue is fixed in 2.1.7.
Description
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.