Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HSummary
CVE-2026-25137 is a critical-severity Missing Authentication for Critical Function (CWE-306) vulnerability. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-14 (Permitted Actions Without Identification or Authentication) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25137 affects the NixOS Odoo package, an open-source ERP and CRM system, in versions from 21.11 up to but not including 25.11 and 26.05. The vulnerability stems from the public exposure of Odoo's database manager interface without any authentication mechanism. In typical non-NixOS setups, a master password provides a secondary defense, but NixOS's immutable configuration prevents Odoo from modifying its own config file to persist an auto-generated or manually set password. As a result, the password is lost on service restarts, leaving the database manager accessible without credentials. This issue is scored at CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H) and maps to CWE-306 (Missing Authentication for Critical Function) and CWE-552 (Files or Directories Accessible to External Parties).
Any unauthenticated attacker with network access to the affected NixOS Odoo instance can exploit this by navigating to the /web/database endpoint. Successful exploitation enables full unauthorized read, download, or deletion of the entire database, including Odoo's file store. No privileges, user interaction, or administrative action are required, making it remotely exploitable over the network with low complexity.
NixOS security advisories and patches, detailed in GHSA-cwmq-6wv5-f3px and related nixpkgs pull requests #485310 and #485454, confirm the fix in Odoo package versions 25.11 and 26.05. Administrators should upgrade to these versions immediately. For detection, review access logs and Odoo logs for requests to /web/database, which indicate potential exploitation attempts.
Indicators from HTTP requests to /web/database can reveal prior unauthorized access, though no widespread real-world exploitation has been reported in the available data.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5405
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 11 hardening rules · 3 OS baselines
V6.2.3V6.4.4V10.4.16V12.1.3
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly enforces authorization checks on access to files and directories, stopping unauthorized external exposure.
Directly mandates unique identification and authentication of users before access to functions requiring identity.
Extends the same authentication requirement to non-organizational users accessing critical functionality.
Requires authentication of services before they can invoke or expose critical functions.
Explicitly identifies and limits actions permitted without authentication, preventing critical functions from being exposed.
AC-6 limits granted privileges, reducing the chance that files or directories become reachable by external parties.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Directly requires authentication of users/services/hardware, which eliminates missing authentication for critical functions.
Enforcing least-privilege permissions and authorization policies directly prevents unauthorized file/directory exposure.
Logical segmentation and access protections stop external parties from reaching files that should remain internal.
Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.
Data-at-rest protections such as encryption or ACLs reduce the impact of unintended file exposure.
Hardened configuration baselines commonly include file-system permission settings that limit external access.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The control explicitly calls for authentication before any critical function is reached, eliminating the possibility of bypassing authentication for high-value operations.
By tracing and retrieving all copies of information stored on endpoint and portable devices, the control reduces the likelihood that files remain accessible outside the organization’s security perimeter.
Labeling information according to its sensitivity and specifying corresponding protection measures makes it less probable that files or directories containing sensitive content will be left accessible to external parties.
Mandating authentication requirements for critical functions at the requirements-gathering stage ensures that essential operations are not left unprotected by missing login or verification mechanisms.
Including asset location and ownership in the inventory, combined with secure disposal procedures, decreases the chance that files or directories remain accessible to external parties after they should have been removed or restricted.
Solid perimeters and locked external access points stop files, devices, or directories containing sensitive data from being reachable by external parties who could otherwise walk in or break in.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (4 rules)
- V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-552
- V-248585 OL 8 must require reauthentication when using the "sudo" command. prevents CWE-306
- V-248597 There must be no "shosts.equiv" files on the OL 8 operating system. prevents CWE-552
RHEL 7 (2 rules)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-306
- V-237635 The Red Hat Enterprise Linux operating system must require re-authentication when using the "sudo" command. prevents CWE-306
RHEL 8 (2 rules)
- V-230492 RHEL 8 must not have the rsh-server package installed. prevents CWE-306
- V-237643 RHEL 8 must require re-authentication when using the "sudo" command. prevents CWE-306