{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-25137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25137 is a critical missing authorization vulnerability in NixOS nixpkgs, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25137 and fix it if it is affected.\n\nWhat it is: CVE-2026-25137 is a critical missing authorization vulnerability in NixOS nixpkgs, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25137 in the wild and no public exploit code.\n\nAffected product: NixOS nixpkgs. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25137/ (Markdown: https://insights.sbomify.com/CVE-2026-25137/index.md)","id":"CVE-2026-25137","markdown":"https://insights.sbomify.com/CVE-2026-25137/index.md","name":"CVE-2026-25137","record":{"aliases":["GHSA-cwmq-6wv5-f3px"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"NixOS Odoo package","requires_auth":"none","summary":"NixOS Odoo setups expose the database manager without authentication, allowing attackers to read and delete the entire database and filestore.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"NixOs Odoo database and filestore publicly accessible with default odoo configuration","id":"CVE-2026-25137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Rucio WebUI has Username Enumeration via Login Error Message","id":"CVE-2026-25138"},"packages":[],"prev":{"headline":"Rucio WebUI has a Reflected Cross-site Scripting Vulnerability","id":"CVE-2026-25136"},"products":["nixpkgs"],"published":"2026-02-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-04","vendors":["NixOS"]},"summary":"NixOS Odoo setups expose the database manager without authentication, allowing attackers to read and delete the entire database and filestore.","url":"https://insights.sbomify.com/CVE-2026-25137/"}