Which versions of Verba are affected by EUVD-2026-46450?

Weaviate Verba, a retrieval-augmented generation platform used by organizations for AI-powered search and knowledge applications, contains a critical vulnerability that allows unauthenticated…

How to fix or mitigate EUVD-2026-46450?

Within 24 hours: Immediately audit and restrict all outbound HTTP/HTTPS connections from Verba 2.1.3 servers through firewall rules, permitting only explicitly approved destinations and third-party APIs required for legitimate RAG operations. Within 7 days: Deploy network segmentation isolating Verba instances from internal systems, cloud metadata endpoints, credential services, and sensitive databases; activate comprehensive logging on all outbound traffic from affected servers to detect exploitation attempts. Within 30 days: Evaluate upgrading to a patched version when Weaviate releases a fix, or migrate to an alternative RAG platform that addresses this vulnerability class; if operational continuity requires continued use of Verba 2.1.3, implement a reverse-proxy gateway with request whitelisting to validate and restrict all outbound connections before they reach your network.

Verba EUVD-2026-46450

Q: What is the CVSS score of EUVD-2026-46450?

EUVD-2026-46450 has a CVSS 4.0 base score of 9.2 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.5%.

| CVE-2026-65317 CRITICAL

Server-Side Request Forgery (SSRF) (CWE-918)

2026-07-21 VulnCheck

GHSA-vmf4-4c4w-vgqh

SSRF Verba Weaviate

9.2

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.2 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.6 HIGH

Remote, low-complexity, unauthenticated via the Origin bypass (PR:N/AC:L); scope changes to reach other systems (S:C) with confidentiality-oriented SSRF impact and no integrity/availability effect.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 21, 2026 - 22:07 vuln.today

CVE Published

Jul 21, 2026 - 21:31 cve.org

CRITICAL 9.2

DescriptionCVE.org

Verba RAG application version 2.1.3 contains a server-side request forgery vulnerability combined with a same-origin middleware bypass that allows unauthenticated remote attackers to make the server issue arbitrary HTTP requests by supplying a crafted Origin header and attacker-controlled host and port values. Attackers can bypass the localhost origin check in the API middleware by sending any Origin value prefixed with ' regardless of port, then submit arbitrary host and port parameters to the /api/connect endpoint to cause the server to issue outbound GET requests to attacker-controlled infrastructure.

AnalysisAI

Server-side request forgery in Weaviate's Verba (GoldenVerba) RAG application version 2.1.3 lets unauthenticated remote attackers coerce the server into issuing arbitrary outbound HTTP GET requests. The flaw stems from a same-origin middleware bypass: any Origin header prefixed with a single quote defeats the localhost origin check, after which attacker-supplied host and port values passed to the /api/connect endpoint are fetched by the server. No public exploit code exists, but a detailed VulnCheck advisory and a third-party technical write-up document the exact bypass; there is no CISA KEV listing and EPSS was not provided.

Technical ContextAI

Verba (also called GoldenVerba) is an open-source Retrieval-Augmented Generation (RAG) web application maintained by Weaviate, identified in CPE as cpe:2.3:a:weaviate:verba. Its Python API layer enforces a same-origin/localhost restriction in middleware to keep the /api/connect functionality private, but the check is string-based and can be short-circuited by prefixing the Origin header with a single-quote character, so an arbitrary Origin (any host/port) is accepted. The root cause maps to CWE-918 (Server-Side Request Forgery): the /api/connect endpoint takes attacker-controlled host and port parameters and uses them to construct an outbound request without validating that the target is a trusted/internal-safe destination, letting the server act as a proxy toward attacker-chosen infrastructure.

RemediationAI

No vendor-released patch identified at time of analysis; the references point to the project repository and advisory write-ups rather than a tagged fixed release, so monitor https://github.com/weaviate/Verba and the VulnCheck advisory for an official patched version and upgrade as soon as one ships. As compensating controls, do not expose the Verba API to untrusted networks - restrict it to a trusted management network or place it behind an authenticating reverse proxy/VPN (trade-off: breaks any intended direct browser access). Enforce strict egress filtering so the server can only reach the specific backend hosts/ports it legitimately needs, blocking outbound traffic to arbitrary internet hosts and to internal metadata/link-local ranges such as 169.254.169.254 (trade-off: may disrupt legitimate connector functionality that /api/connect drives). At the proxy, reject requests whose Origin header does not exactly match an allowlisted trusted origin rather than relying on Verba's prefix-based check (trade-off: requires maintaining the allowlist as deployment hosts change).