# CVE-2026-56399 — open-webui

> As of 2026-07-01, CVE-2026-56399 is a MEDIUM-severity vulnerability in open-webui, CVSS v3.1 5, EPSS 0.3% (23.8th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-56399 as of 2026-07-01; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-01

## What is CVE-2026-56399?

Open WebUI before 0.6.27 contains a server-side request forgery vulnerability in the /api/v1/retrieval/process/web endpoint that allows authenticated users to bypass SSRF protections. Attackers can manipulate URL parameters with location redirect headers to access internal services and potentially execute commands via instance secrets.

The record classifies CVE-2026-56399 under weakness class [CWE-918](https://intel.threadlinqs.com/cwe/CWE-918). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 97 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **CVSS v4.0 base score:** 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 23.8% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-06-30, last modified 2026-07-01

## Is CVE-2026-56399 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [open-webui](https://intel.threadlinqs.com/vendors/open-webui): open-webui

## How to fix CVE-2026-56399

No vendor patch reference has been recorded for CVE-2026-56399 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-56399

No threat campaign in the Threadlinqs corpus currently references CVE-2026-56399, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-07-02. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/open-webui/open-webui/security/advisories/GHSA-82r6-c5jm-f3mw)
- [github.com — patch](https://github.com/open-webui/open-webui/commit/02238d3113e966c353fce18f1b65117380896774)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/open-webui-server-side-request-forgery-via-location-redirect-in-api-v1-retrieval-process-web)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-56399
Full detection coverage and IOCs for threats exploiting CVE-2026-56399 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp
