⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.5

How to Fix CVE-2026-45331: SSRF Vulnerability in open-webui

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.5 - High
Actively exploited?Not currently listed in CISA KEV
Affected< 0.9.0
Fixed in0.9.0.
Type (CWE)CWE-918: Server-Side Request Forgery (SSRF)

What is CVE-2026-45331?

CVE-2026-45331 is an server-side request forgery (SSRF) flaw in open-webui. The product makes server-side HTTP requests to attacker-controlled URLs, exposing internal services and cloud metadata endpoints. Vendor description: Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.0, validate_url() in backend/open_webui/retrieval/web/utils.py calls validators.ipv6(ip, private=True), but the validators library does NOT implement the private keyword for IPv6 , the call raises a ValidationError (which is falsy in a boolean context), so every IPv6 address passes the filter.

Why this CVE matters

Server-side request forgery routinely chains into cloud-metadata theft, internal service enumeration, and credential exfiltration. In cloud-hosted deployments the impact is often more severe than on-prem because of the metadata service exposure.

For deployments of open-webui that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open open-webui's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-45331

  1. Read the vendor advisory in full: https://github.com/open-webui/open-webui/security/advisories/GHSA-4v7r-f4w8-8972
  2. Upgrade open-webui to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade open-webui open-webui


# CVE-2026-45331 affects open-webui < 0.9.0.
# Fixed in 0.9.0. Vendor advisory: https://github.com/open-webui/open-webui/security/advisories/GHSA-4v7r-f4w8-8972

# 1. Identify the running version using the vendor-documented command.
#    (Open the product UI -> About, or run the CLI version probe.)

# 2. Stage the patched build named in the advisory.
#    Vendor advisory: https://github.com/open-webui/open-webui/security/advisories/GHSA-4v7r-f4w8-8972

# 3. Apply the upgrade. If the vendor ships a Linux package, pull it via your
#    distribution's package manager:
sudo apt update && sudo apt install --only-upgrade open-webui        # Debian / Ubuntu
sudo dnf upgrade open-webui                                          # RHEL / Rocky / Alma / Fedora

# 4. Restart the affected service so the new binary loads.
sudo systemctl restart open-webui 2>/dev/null || true

# 5. Re-run the version probe and confirm it matches 0.9.0.


# Windows-hosted installs of open-webui: apply via PSWindowsUpdate or the vendor MSI.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

Verify the fix landed


# CVE-2026-45331 verification checklist.

# 1. Confirm the running version matches 0.9.0 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-45331.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://github.com/open-webui/open-webui/security/advisories/GHSA-4v7r-f4w8-8972

If you cannot patch immediately

Block outbound network access from the affected service to internal subnets and cloud metadata endpoints (e.g. 169.254.169.254). Apply the patched build.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-45331 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-45331?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for open-webui run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*