Odoo · versions

Odoo 18 security vulnerabilities

Odoo 18 ships as Odoo Community (open source) and Odoo Enterprise (proprietary). Public patch evidence on this site covers Community Git only.

Evidence status

1 version-linked advisories are attributed in this catalog (1 via branch-linked fix commits). Zero matches is never proof Odoo 18 is secure. 29 Community commits on 18.0 are flagged as security candidates in private analysis; only disclosed public fixes appear below. Coverage can lag vendor disclosure. Always verify the original advisory.

Version overview

  • Odoo 18 is a major Odoo series used by ERP administrators and hosting providers.
  • Security posture depends on the exact Community (and optional Enterprise) revision you run — not only the major version number.
  • Vendor advisories, backport policy, and installed modules all change exposure. A quiet CVE list is not a clean bill of health.

Security advisories for Odoo 18

Confirmed catalog rows attributed to this version series via affected ranges, advisory text, or CVE-linked fix commits on 18.0.

Patch information

Public, disclosed Community fix commits attributed to 18.0. Proprietary Enterprise diffs are never shown.

  1. Jun 5, 2024

    [REF] web_tour: prepare to change the default action in tour_compiler

    CVE-2019-11786 · 4cc6ca11801c · GitHub

Disclosed public references on file for 18.0: 1.

Security changes & hardening

Follow the Odoo security updates timeline for confirmed fixes, dependency remediations, and hardening events. Ordinary bugfixes are excluded from that timeline.

How to identify your installed revision

  1. From the Odoo shell: open the database manager or Settings → About to read the build / commit when exposed by your packaging.
  2. On source installs, run `git -C /path/to/odoo rev-parse HEAD` on the Community repository (and Enterprise if authorized).
  3. Container or Debian packages: map the package version to the upstream commit your vendor documents — do not assume the tag equals a security backport.
  4. Record both the major series (e.g. 18.0) and the full SHA before asking whether a disclosed fix is present.

Security checker

Paste your Community SHA to see whether disclosed fixes for 18.0 are already ancestors of your revision.

Monitoring

Watch the Odoo stack for newly ingested advisories. Alerts follow your account package — they do not invent exploitability for Odoo 18.

Create an account to monitor Odoo

Broader Odoo catalog

56 records

Other recent Odoo findings that are not tied to Odoo 18. Use each CVE’s version checker before you treat one as in range.

Odoo 18 security vulnerabilities · ZeroDay Findings