CVE-2026-0767
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 Cleartext Transmission of Credentials Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of Open WebUI. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of credentials provided to the endpoint. The issue results from transmitting sensitive information in plaintext. An attacker can leverage this vulnerability to disclose transmitted credentials, leading to further compromise. Was ZDI-CAN-28259.
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 transmits user credentials in plaintext when authenticating to certain endpoints. An unauthenticated attacker on the adjacent network can intercept these credentials by sniffing network traffic, potentially gaining unauthorized access to the application and further compromising user accounts.
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.6.32CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Check installed Open WebUI versionRun the command to display the installed version of Open WebUI (e.g., check the Docker image tag, Helm chart version, or application UI footer/splash screen)Affected if The installed version is exactly 0.6.32
-
Verify HTTPS is enabled on the serverInspect the server configuration files or environment variables to confirm SSL/TLS is configured. For Docker deployments, check for the --tls-cert and --tls-key flags or equivalent configuration. Look for the presence of an SSL certificate file and private key on the server.Affected if HTTPS/TLS is not enabled or SSL certificates are not configured
-
Confirm authentication endpoints use HTTPSReview the web server or reverse proxy configuration (e.g., nginx, Apache, or built-in server) to ensure all authentication-related endpoints (login, session token exchange) are routed through HTTPS. Check for HTTP to HTTPS redirects on auth routes.Affected if Authentication endpoints are accessible over HTTP or redirect to HTTP instead of enforcing HTTPS
-
Inspect network traffic configurationCheck if the web server or application is configured to enforce TLS 1.2 or higher and disable insecure cipher suites. Look for configuration parameters related to secure transport in the server settings.Affected if TLS enforcement is disabled or weak cipher suites are allowed
A user is affected if they are running Open WebUI version 0.6.32 AND the authentication endpoints are not properly configured to use HTTPS/TLS encryption.
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.
From vendor dataEnable TLS/SSL encryption for all network communications, particularly on authentication endpoints. Configure proper HTTPS with valid certificates and enforce secure transport.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0767 — 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-0767 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