CVE-2025-15603 ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.
Not scored
Published
Updated
Check this codebase for CVE-2025-15603 and fix it if it is affected.
What it is: CVE-2025-15603 is a vulnerability, published on 9 Mar 2026.
Exploitation: There is no known exploitation of CVE-2025-15603 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-2025-15603/ (Markdown: https://insights.sbomify.com/CVE-2025-15603/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-15603?
CVE-2025-15603 is a vulnerability, published on 9 Mar 2026.
Official description
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The vendor explains: "The 't0p-s3cr3t' default was dead code on every supported startup path: start.sh, start_windows.bat and
open-webui serve all set or auto-generate WEBUI_SECRET_KEY before the backend imports env.py. It was only ever reachable by invoking uvicorn directly, which is unsupported and unsafe (the app would then sign tokens/cookies with a public, hardcoded key)."Which versions are affected by CVE-2025-15603?
How do I fix CVE-2025-15603?
No fix has been published for CVE-2025-15603 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-15603 being exploited?
There is no known exploitation of CVE-2025-15603 in the wild and no public exploit code.