CVE-2026-0767 Open WebU's investigation showed that this describes the behavior of plain HTTP rather than a defect in the product.
Not scored
Published
Updated
Check this codebase for CVE-2026-0767 and fix it if it is affected.
What it is: CVE-2026-0767 is a vulnerability, published on 23 Jan 2026.
Exploitation: There is no known exploitation of CVE-2026-0767 in the wild and no public exploit code.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-0767/ (Markdown: https://insights.sbomify.com/CVE-2026-0767/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-0767?
CVE-2026-0767 is a vulnerability, published on 23 Jan 2026.
Official description
Open WebU's investigation showed that this describes the behavior of plain HTTP rather than a defect in the product. TLS termination is the operator's deployment decision, as it is for any backend that speaks HTTP, and not a security issue. https://docs.openwebui.com/security/vendor-dispositions/cve-2026-0767
Which versions are affected by CVE-2026-0767?
How do I fix CVE-2026-0767?
No fix has been published for CVE-2026-0767 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-0767 being exploited?
There is no known exploitation of CVE-2026-0767 in the wild and no public exploit code.