CVE-2022-26662
HIGHCVE-2022-26662 is a high-severity (CVSS 7.5) CWE-776 vulnerability in trytond. O3 Security confirms whether CVE-2022-26662 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
XML Entity Expansion in trytond and proteus
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.46 |
| 🐍PyPI | trytond | ≥ 6.0.0&&< 6.0.16 | 6.0.16 |
| 🐍PyPI | trytond | ≥ 6.1.0&&< 6.2.6 | 6.2.6 |
| 🐍PyPI | proteus | ≥ 5.0.0&&< 5.0.12 | 5.0.12 |
| 🐍PyPI | proteus | ≥ 6.0.0&&< 6.0.5 | 6.0.5 |
| 🐍PyPI | proteus | ≥ 6.1.0&&< 6.2.2 | 6.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trytond. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-26662 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-26662. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-26662 in your dependencies?
O3 detects CVE-2022-26662 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.