CVE-2026-56399

MEDIUMPre-NVD 5.05.0
EchelonGraph scoreHIGH confidence

Score 5.0 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.0
EG Score
5.0(high)
EPSS
23.9%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (3)

Auto-updated Jul 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Full 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-f3mw
generic

Open 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-web
github_commit

commit 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/02238d3113e966c353fce18f1b65117380896774

Vendor 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 22× in last 7d / 22× 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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 11:34 UTCEG score recompute
  4. 2026-07-06 11:34 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 09:31 UTCEG score recompute
  8. 2026-07-05 09:31 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 07:30 UTCEG score recompute
  12. 2026-07-04 07:30 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 05:29 UTCEG score recompute
  16. 2026-07-03 05:29 UTCGHSA enrichment
  17. 2026-07-02 03:20 UTCEG score recompute
  18. 2026-07-02 03:20 UTCGHSA enrichment
  19. 2026-07-01 17:06 UTCNVD updateCVSS v4 → 5.3
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 01:19 UTCEG score recompute
  22. 2026-07-01 01:19 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56399?
CVE-2026-56399 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-56399 disclosed?
CVE-2026-56399 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56399 actively exploited?
CVE-2026-56399 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56399?
CVE-2026-56399 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-56399?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56399, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56399

Explore →

Is Your Infrastructure Affected by CVE-2026-56399?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.