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.
CVE-2026-65317
This high-severity CVE scores 8.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(low)
- EPSS
- 38.6%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 21, 2026
Advisory Details (3)
Auto-updated Jul 22, 2026Verba (goldenverba) Server-Side Request Forgery via /api/connect and Same-Origin Middleware Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/verba-goldenverba-server-side-request-forgery-via-api-connect-and-same-origin-middleware-bypassGitHub - weaviate/Verba: Retrieval Augmented Generation (RAG) chatbot powered by Weaviate · GitHub
https://github.com/weaviate/Verbaoss/verba.md at main · geo-chen/oss · GitHub
https://github.com/geo-chen/oss/blob/main/verba.md#finding-2-ssrf--same-origin-middleware-bypass-in-apiconnect----goldenverbaVendor Advisories for CVE-2026-65317(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 23:09 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-65317?
When was CVE-2026-65317 disclosed?
Is CVE-2026-65317 actively exploited?
What is the CVSS score of CVE-2026-65317?
How do I remediate CVE-2026-65317?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65317
Is Your Infrastructure Affected by CVE-2026-65317?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.