CVE-2026-65318: Verba (goldenverba) Unauthenticated Server-Side Request Forgery via WebSocket Import Endpoint HTMLReader
Verba RAG application version 2.1.3 contains an unauthenticated server-side request forgery vulnerability that allows unauthenticated attackers to cause the backend to issue arbitrary HTTP GET requests by supplying attacker-controlled URLs through the WebSocket import endpoint. Attackers can connect to the /ws/import_files WebSocket endpoint without authentication, specify arbitrary URLs in the HTMLReader configuration, and cause the server to fetch internal resources such as co-located database endpoints or cloud instance metadata services to retrieve sensitive credentials.
Security readout for executives and security teams
Plain-English summary
Verba 2.1.3 has a critical unauthenticated SSRF issue. If the import WebSocket is reachable, an outside attacker may cause the backend to fetch internal URLs, including metadata or database endpoints, potentially exposing sensitive credentials. No active exploitation is stated in the provided sources.
Executive priority
Prioritize exposed Verba systems immediately. The likely business impact is credential or internal service exposure from a server-side network pivot, with no authentication required according to the sources.
Technical view
CVE-2026-65318 is CWE-918 in Verba's WebSocket import flow using HTMLReader. The source bundle says unauthenticated users can supply attacker-controlled URLs and cause backend HTTP GET requests. CVSS v4.0 is 9.2. Version details conflict: the description names 2.1.3, while affected metadata lists version "0".
Likely exposure
Highest exposure is internet-accessible or untrusted-network Verba deployments with the import WebSocket enabled. Risk increases where Verba can reach cloud metadata services, internal APIs, databases, or credential-bearing endpoints from its server-side network position.
Exploitation context
The sources describe unauthenticated remote reachability and sensitive credential retrieval risk, but do not state confirmed exploitation. KEV is false in the bundle. Treat public-facing deployments as urgent until vendor guidance or exposure testing confirms otherwise.
Researcher notes
Do not assume a fixed version range beyond the provided sources. Focus validation on reachability, authentication enforcement, server-side egress, and evidence of unexpected backend fetches. Avoid intrusive testing against internal metadata or credential services without authorization.
Mitigation direction
Check Weaviate Verba vendor guidance for patched versions or official remediation.
Remove public access to the Verba import WebSocket until remediated.
Require authentication or trusted-network access in front of Verba.
Restrict server egress to block metadata, database, and internal-only endpoints.
Disable URL-based HTML import if operationally feasible.
Validation and detection
Inventory Verba deployments and confirm whether version 2.1.3 is present.
Identify whether the import WebSocket is reachable from untrusted networks.
Review reverse proxy and application logs for unexpected import WebSocket activity.
Review outbound network logs for Verba requests to internal or metadata endpoints.
Confirm egress controls prevent Verba from reaching sensitive internal services.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.