VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

odoo: vulnerability history, versions and safety

odoo is a package in the Debian ecosystem. Vulert records 36 vulnerabilities for it across 26 releases, from Dec 2020 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded U36
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all odoo vulnerabilities

Vulert verdict on odoo i

Updated on 23 Oct 2026

Careful: 2 of the 36 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 36 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 36 over 4 years · 0 in the last year i
  • Latest disclosure 25 Feb 2025 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for odoo, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 26 of 26 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 10
  • 2023 23
  • 2024 1
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 36 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for odoo

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
OAuth Token Export Vulnerability in Odoo Packages 8.8 high No fix published 25 Feb 2025
File Access Vulnerability in Odoo Package: CVE-2021-23166 8.7 high 14.0.0+dfsg.2-7+deb11u1 25 Apr 2023
Sandboxing Vulnerability in Odoo Package Allows Unauthorized Database Access 8.7 high 14.0.0+dfsg.2-7+deb11u1 25 Apr 2023
Improper Access Control in Odoo Package Allows Unauthorized Data Creation 8.1 high 14.0.0+dfsg.2-7+deb11u1 25 Apr 2023
Improper Access Control in Odoo Package Leading to Unauthorized Payment Validation 7.5 high 14.0.0+dfsg.2-7+deb11u1 25 Apr 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About odoo

Is odoo safe to use?

Vulert records 36 vulnerabilities for odoo in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 36 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does odoo have?

36 vulnerabilities are recorded for odoo in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 36 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new odoo vulnerabilities disclosed?

0 vulnerabilities were recorded for odoo in the last 12 months, and the oldest entry in this database dates to 22 Dec 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of odoo are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor odoo for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the odoo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.