CVE-2026-65317 Overview
CVE-2026-65317 is a server-side request forgery (SSRF) vulnerability in Verba (goldenverba) RAG application version 2.1.3. The flaw combines an SSRF weakness in the /api/connect endpoint with a same-origin middleware bypass. Unauthenticated remote attackers can force the Verba server to issue arbitrary outbound HTTP GET requests to attacker-controlled infrastructure. The middleware only checks that the Origin header begins with a specific prefix, allowing trivial bypass regardless of port. This vulnerability is tracked as CWE-918: Server-Side Request Forgery.
Critical Impact
Unauthenticated attackers can pivot the Verba server into internal networks, reach cloud metadata endpoints, and exfiltrate sensitive data via server-initiated HTTP requests.
Affected Products
- Verba (goldenverba) version 2.1.3
- Weaviate Verba RAG application deployments exposing /api/connect
- Self-hosted Verba instances relying on the same-origin middleware for API protection
Discovery Timeline
- 2026-07-21 - CVE-2026-65317 published to NVD
- 2026-07-21 - Last updated in NVD database
Technical Details for CVE-2026-65317
Vulnerability Analysis
Verba is an open-source retrieval-augmented generation (RAG) application maintained by Weaviate. The /api/connect endpoint accepts user-supplied host and port values, then issues outbound HTTP GET requests to the constructed URL. An API middleware component was intended to restrict access to same-origin (localhost) requests only. However, the origin validation logic only checks whether the Origin header string begins with a specific prefix and does not enforce a strict allowlist or verify the port.
An unauthenticated attacker can send a request carrying any Origin header value that begins with the accepted prefix, then supply arbitrary host and port parameters. The server then dispatches an HTTP request to the attacker-specified destination. This grants the attacker a network pivot from the perspective of the Verba host. Refer to the VulnCheck SSRF Advisory and public PoC writeup for reproduction details.
Root Cause
The root cause is improper input validation in two places. First, the same-origin middleware performs a prefix-based string comparison on the Origin header instead of parsing and matching the full origin tuple of scheme, host, and port. Second, the /api/connect handler uses unvalidated host and port parameters directly in an outbound request without allowlisting internal destinations or blocking private address ranges.
Attack Vector
Exploitation requires only network access to the Verba HTTP interface. The attacker crafts an HTTP request to /api/connect with an Origin header that satisfies the flawed prefix check and supplies host and port parameters pointing to a target service. The Verba server then issues a GET request to that target. Attackers can use this to probe internal services, query cloud instance metadata services (IMDS) for credentials, or exfiltrate responses containing sensitive configuration data. Public proof-of-concept material is available in the GitHub PoC for SSRF.
Detection Methods for CVE-2026-65317
Indicators of Compromise
- Requests to /api/connect from external IP addresses containing non-standard host and port parameter values
- HTTP requests with Origin headers that pass the prefix check but originate from remote clients
- Outbound connections from the Verba server process to internal RFC1918 ranges or cloud metadata addresses such as 169.254.169.254
- Unexpected DNS lookups initiated by the Verba host for attacker-controlled domains
Detection Strategies
- Inspect web server and reverse proxy logs for POST or GET requests to /api/connect and correlate the Origin header with the source IP
- Alert on Verba process network egress to non-application destinations, especially metadata endpoints and internal management interfaces
- Deploy web application firewall (WAF) rules that block /api/connect requests carrying host values resolving to internal or link-local ranges
Monitoring Recommendations
- Log all requests to Verba API endpoints with full header and parameter capture for retrospective analysis
- Monitor for anomalous outbound HTTP traffic patterns from RAG application hosts, particularly to unfamiliar domains
- Track authentication and middleware bypass indicators through centralized logging with correlation across proxy and application tiers
How to Mitigate CVE-2026-65317
Immediate Actions Required
- Restrict network access to the Verba /api/connect endpoint using upstream firewall or reverse proxy rules until a patch is applied
- Deploy egress filtering on the Verba host to block outbound traffic to internal address ranges and cloud metadata IPs
- Remove or isolate Verba 2.1.3 deployments from internet-facing exposure
- Rotate any credentials retrievable from the local metadata service if exposure is suspected
Patch Information
At time of publication, no fixed release identifier is listed in the NVD entry. Monitor the Verba GitHub repository and the VulnCheck advisory for updates. Upgrade beyond version 2.1.3 once a patched build addressing both the SSRF and the middleware bypass is published.
Workarounds
- Place Verba behind an authenticating reverse proxy that enforces strict origin validation and rejects any request lacking valid session credentials
- Block the /api/connect route entirely at the proxy layer if the connect functionality is not required
- Enforce host-based egress allowlists so the Verba process can only reach approved external services
- Run Verba in a network segment without route access to internal management interfaces or cloud metadata services
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
