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.
CVE-2026-56399
Score 5.0 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 5.0; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.0
- EG Score
- 5.0(high)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity50% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 2, 2026
Advisory Details (3)
Auto-updated Jul 6, 2026Full SSRF with user role on endpoint /api/v1/retrieval/process/web via location redirect · Advisory · open-webui/open-webui · GitHub
https://github.com/open-webui/open-webui/security/advisories/GHSA-82r6-c5jm-f3mwOpen WebUI - Server-Side Request Forgery via Location Redirect in /api/v1/retrieval/process/web | Advisories | VulnCheck
https://www.vulncheck.com/advisories/open-webui-server-side-request-forgery-via-location-redirect-in-api-v1-retrieval-process-webcommit 02238d3113e9 (open-webui/open-webui)
Fix landed in open-webui/open-webui commit 02238d3113e9 — awaiting tagged release
https://github.com/open-webui/open-webui/commit/02238d3113e966c353fce18f1b65117380896774Vendor Advisories for CVE-2026-56399(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 9× in last 7d / 56× 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-26 14:54 UTCEPSS rescore
- 2026-07-26 13:32 UTCEG score recompute
- 2026-07-26 13:31 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 05:46 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 03:44 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 01:43 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 23:43 UTCGHSA enrichment
Show 31 moreShow fewer
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 21:42 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 19:41 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:40 UTCGHSA enrichment
- 2026-07-08 15:38 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:35 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 11:34 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 09:31 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 07:30 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 05:29 UTCGHSA enrichment
- 2026-07-02 03:20 UTCGHSA enrichment
- 2026-07-01 17:06 UTCNVD updateCVSS v4 → 5.3
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 01:19 UTCEG score recompute
- 2026-07-01 01:19 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-14721EG 10.0EPSS p95CRITICAL
- CVE-2018-18843EG 10.0CRITICAL
- CVE-2018-19047EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-3774EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2018-1789NVD 8.4EG 9.9CRITICAL
Frequently asked(5)
What is CVE-2026-56399?
When was CVE-2026-56399 disclosed?
Is CVE-2026-56399 actively exploited?
What is the CVSS score of CVE-2026-56399?
How do I remediate CVE-2026-56399?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56399
Is Your Infrastructure Affected by CVE-2026-56399?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.