CVE-2022-26662 — trytond
HIGHCVE-2022-26662 is a high-severity (CVSS 7.5) CWE-776 vulnerability in trytond. A fix is available for trytond — see the affected versions and patch details below.
XML Entity Expansion in trytond and proteus
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-26662 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
trytond🐍trytond🐍trytond🐍proteus🐍proteus🐍proteusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
An XML Entity Expansion (XEE) issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An unauthenticated user can send a crafted XML-RPC message to consume all the resources of the server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | trytond | ≥ 5.0.0&&< 5.0.46 | 5.0.46pip install --upgrade 'trytond==5.0.46' |
| 🐍PyPI | trytond | ≥ 6.0.0&&< 6.0.16 | 6.0.16pip install --upgrade 'trytond==6.0.16' |
| 🐍PyPI | trytond | ≥ 6.1.0&&< 6.2.6 | 6.2.6pip install --upgrade 'trytond==6.2.6' |
| 🐍PyPI | proteus | ≥ 5.0.0&&< 5.0.12 | 5.0.12pip install --upgrade 'proteus==5.0.12' |
| 🐍PyPI | proteus | ≥ 6.0.0&&< 6.0.5 | 6.0.5pip install --upgrade 'proteus==6.0.5' |
| 🐍PyPI | proteus | ≥ 6.1.0&&< 6.2.2 | 6.2.2pip install --upgrade 'proteus==6.2.2' |
Affected Products
debian linuxdebianproteustrytontrytondtrytonDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trytond, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update trytond to 5.0.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-26662 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-26662 in your dependencies?
Find it across PyPI, including transitive dependencies.