# CVE-2026-65317: Verba (goldenverba) Server-Side Request Forgery via /api/connect and Same-Origin Middleware Bypass

> Unauthenticated attackers can bypass origin checks to force the Verba server to issue arbitrary HTTP requests, enabling internal network scanning and data exfiltration.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-vmf4-4c4w-vgqh

## What is CVE-2026-65317?

CVE-2026-65317 is a critical server-side request forgery vulnerability in Weaviate Verba, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-65317?


## How do I fix CVE-2026-65317?

No fix has been published for CVE-2026-65317 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65317 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65317 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65317 and fix it if it is affected.

What it is: CVE-2026-65317 is a critical server-side request forgery vulnerability in Weaviate Verba, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65317 exists.

Affected product: Weaviate Verba. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65317/ (Markdown: https://insights.sbomify.com/CVE-2026-65317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65317
- OSV: https://osv.dev/vulnerability/CVE-2026-65317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65317/
Summaries are generated and may contain mistakes; the official description above is the record.
