CVE-2020-29396

CVE-2020-29396 is a high-severity vulnerability in Odoo with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-267.

Key facts

Description

A sandboxing issue in Odoo Community 11.0 through 13.0 and Odoo Enterprise 11.0 through 13.0, when running with Python 3.6 or later, allows remote authenticated users to execute arbitrary code, leading to privilege escalation.

Frequently asked questions

What is CVE-2020-29396?
A sandboxing issue in Odoo Community 11.0 through 13.0 and Odoo Enterprise 11.0 through 13.0, when running with Python 3.6 or later, allows remote authenticated users to execute arbitrary code, leading to privilege escalation.
How severe is CVE-2020-29396?
CVE-2020-29396 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-29396 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-29396?
CVE-2020-29396 primarily affects Odoo. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-29396?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-29396 published?
CVE-2020-29396 was published on 2020-12-22 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Odoo

All CVEs affecting Odoo →

Other CWE-267 vulnerabilities

Browse all CWE-267 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: