CVE-2026-25137: NixOS nixpkgs · Exposed Files or Directories
Affects NixOS nixpkgsSource CVE Database V5
Not known to be exploited · 10% EPSS · CVSS 9.1 Critical : upgrade to 25.11 as a priority.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 10.4% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 25.11
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade NixOS nixpkgs to 25.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NixOSnixpkgs | Affected
| Fixed in
|
AI-suggested
European organizations should immediately upgrade affected NixOS Odoo packages to versions 25.11 or 26.05 where the vulnerability is fixed. Until upgrades are applied, network-level mitigations must be enforced, such as restricting access to the Odoo database manager interface via firewall rules or VPNs to trusted internal users only. Organizations should audit their NixOS Odoo deployments to identify any publicly exposed /web/database endpoints and block external access. Monitoring and analyzing HTTP access logs for requests to /web/database can help detect exploitation attempts early. Implementing network segmentation to isolate Odoo servers and applying strict access controls will reduce exposure. Additionally, organizations should consider deploying Web Application Firewalls (WAFs) with rules to block unauthorized access to the database manager path. Regular backups of Odoo databases and file stores should be maintained to enable recovery in case of data deletion. Finally, educating system administrators about the unique configuration challenges of NixOS and Odoo password persistence can prevent misconfigurations leading to exposure.
Description
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.