CVE-2026-25137
CRITICALEPSS 95th pctlDescription
The NixOs Odoo package is an open source ERP and CRM system. From 21.11 to before 25.11 and 26.05, every NixOS based Odoo setup publicly exposes the database manager without any authentication. This allows unauthorized actors to delete and download the entire database, including Odoos file store. Unauthorized access is evident from http requests. If kept, searching access logs and/or Odoos log for requests to /web/database can give indicators, if this has been actively exploited. The database manager is a featured intended for development and not meant to be publicly reachable. On other setups, a master password acts as 2nd line of defence. However, due to the nature of NixOS, Odoo is not able to modify its own configuration file and thus unable to persist the auto-generated password. This also applies when manually setting a master password in the web-UI. This means, the password is lost when restarting Odoo. When no password is set, the user is prompted to set one directly via the database manager. This requires no authentication or action by any authorized user or the system administrator. Thus, the database is effectively world readable by anyone able to reach Odoo. This vulnerability is fixed in 25.11 and 26.05.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Exploit Intelligence
High risk: more likely to be exploited than 95% of all known CVEs.
References
Related Vulnerabilities
Other CWE-306 (Missing Authentication for Critical Function) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2017-10271 | High | 7.5 | 100% | KEV + Ransom | - |
| CVE-2023-42793 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2022-1388 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2026-33017 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2021-37415 | Critical | 9.8 | 100% | KEV | - |
Common questions
How do I fix CVE-2026-25137?
No published fix for CVE-2026-25137 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-25137 being actively exploited?
Not that we know of. CVE-2026-25137 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 9.5% is the estimated probability that it will be exploited in the next 30 days. That is higher than 95% of all scored CVEs.
How severe is CVE-2026-25137?
CVE-2026-25137 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-25137
Markdown
[](https://tridentstack.com/cve/CVE-2026-25137)HTML
<a href="https://tridentstack.com/cve/CVE-2026-25137"><img src="https://tridentstack.com/cve/badge/CVE-2026-25137.svg" alt="CVE-2026-25137"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-02-03.