CVE-2026-45299
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpen WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.8.0, the profile_image_url field on the user profile update form accepted arbitrary data: URI values without MIME-type validation, resulting in a XSS vulnerability. This vulnerability is fixed in 0.8.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpen WebUI prior to version 0.8.0 contains a stored XSS vulnerability in the user profile update form. The profile_image_url field accepts data: URI values without validating the MIME type, allowing attackers to inject arbitrary JavaScript through crafted data URIs that bypass expected image type restrictions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your Open WebUI versionLocate the installed version of Open WebUI by checking the application metadata, container tag, or the version file included in your deployment. Common locations include the Dockerfile, docker-compose.yml, or a VERSION file in the application root.Affected if The installed version is below 0.8.0
-
Verify the profile update form existsAccess the user profile settings interface in your Open WebUI instance and locate the profile_image_url field or avatar upload functionality.Affected if The profile update form with an image URL or avatar field is present and accessible to users
-
Test for data: URI acceptanceSubmit a test data: URI in the profile_image_url field using a non-image MIME type (for example, a data: URI containing text or script content instead of an image). Observe whether the application accepts and stores the value without rejecting it based on MIME type validation.Affected if The application accepts data: URIs with non-image MIME types in the profile_image_url field without validation errors
-
Inspect stored profile dataAfter submitting a test value, retrieve the stored profile data from the database or user profile display to confirm the data: URI was saved as-is without sanitization or MIME type enforcement.Affected if The submitted data: URI is stored and rendered without MIME type validation or content filtering
You are affected if Open WebUI version is below 0.8.0 and the profile_image_url field accepts and stores data: URIs without validating that they contain actual image content types.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.8.0
Upgrade Open WebUI to version 0.8.0 or later. If immediate patching is not possible, implement server-side MIME-type validation on the profile_image_url field to reject non-image content types.
0.8.0
- Back up the current Open WebUI installation and any associated database
- Upgrade Open WebUI to version 0.8.0 or later using the appropriate installation method (e.g., Docker, pip, or source)
- After upgrade, verify that the profile_image_url field now properly validates MIME types for uploaded images
- Test that user profile updates work correctly with valid image URLs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45299 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data