Skip to content
Heist/ feed
Back to feed
Critical

NixOs Odoo database and filestore publicly accessible with default odoo configuration

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-25137
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 08:27 UTC · Revision 1

Source evidence

NixOs Odoo database and filestore publicly accessible with default odoo configuration

core-osv · Original source

Published 2 Feb 2026, 22:47 UTC

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.

osv:CVE-2026-25137
Complete source record
{
  "id": "21941807d2aff4403034e58387383f8daedd98970a13c996432716fcc9c3c228",
  "url": "https://osv.dev/vulnerability/CVE-2026-25137",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "NixOs Odoo database and filestore publicly accessible with default odoo configuration",
    "summary": "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.",
    "evidence": "osv:CVE-2026-25137",
    "products": [],
    "severity": "critical",
    "structured": {
      "id": "CVE-2026-25137",
      "aliases": [
        "CVE-2026-25137",
        "GHSA-cwmq-6wv5-f3px"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/nixos/nixpkgs",
              "type": "GIT",
              "events": [
                {
                  "introduced": "b889a3f7a07515108cc9614639cd307cf2acbec5"
                },
                {
                  "fixed": "e56e0beed4312a89b60fe312ee2241f7a1627f76"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "21.11"
                      },
                      {
                        "fixed": "25.11"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "25.11"
                      }
                    ],
                    "source": "DESCRIPTION"
                  }
                ]
              }
            }
          ],
          "versions": [
            "24.11-pre",
            "24.05-pre",
            "23.11-beta",
            "23.11-pre",
            "23.05-pre",
            "21.11-pre"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-25137.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:27.355503773Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/25xxx/CVE-2026-25137.json",
        "https://github.com/NixOS/nixpkgs/security/advisories/GHSA-cwmq-6wv5-f3px",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-25137",
        "https://github.com/NixOS/nixpkgs/pull/485310",
        "https://github.com/NixOS/nixpkgs/pull/485454"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-306",
          "CWE-552"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/25xxx/CVE-2026-25137.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-25137",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 493830,
  "published_at": "2026-02-02T22:47:50.167+00:00"
}