# CVE-2025-66423: trytond β€” Fixed in 7.6.11 🐍 🐍 PyPI Not in CISA KEV HIGH severity # CVE-2025-66423 β€” trytond HIGH CVE-2025-66423 is a high-severity (CVSS 7.1) CWE-863 vulnerability in trytond. A fix is available for trytond β€” see the affected versions and patch details below. trytond does not enforce access rights for the route of the HTML editor. Also known as[GHSA-p3p5-xrmv-4j6x](/vulnerability/GHSA-p3p5-xrmv-4j6x)PYSEC-2026-1991 Published Nov 30, 2025 Updated Jul 7, 2026 Affected 4 pkgs Patched 4 / 4 Exploits None indexed Exploitation data as of Nov 8, 2026 Β· OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66423. ## EPSS Exploitation Probability [via FIRST.org β†—](https://www.first.org/epss/) 0.2%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs15th percentile β€” riskier than 15% of all scored CVEsHighest risk 0.00%0.25%0.49%0.74%0.0%0.2%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 4 pkgs affected 🐍`trytond`🐍`trytond`🐍`trytond`🐍`trytond` Real-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 Tryton trytond 6.0 before 7.6.11 does not enforce access rights for the route of the HTML editor. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.70. ## Affected Packages 4 total 4 fixed Ecosystem Package Vulnerable range Fix 🐍PyPI `trytond` β‰₯ 7.5.0&&< 7.6.11 7.6.11`pip install --upgrade 'trytond==7.6.11'` 🐍PyPI `trytond` β‰₯ 7.1.0&&< 7.4.21 7.4.21`pip install --upgrade 'trytond==7.4.21'` 🐍PyPI `trytond` β‰₯ 7.0.0&&< 7.0.40 7.0.40`pip install --upgrade 'trytond==7.0.40'` 🐍PyPI `trytond` β‰₯ 6.0.0&&< 6.0.70 6.0.70`pip install --upgrade 'trytond==6.0.70'` ## Affected Products 1 product Β· 4 configurations Application `trytond`tryton β‰₯ 7.6.0 && < 7.6.11 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect 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. 2. ### Fix Update trytond to 7.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range β€” O3 confirms CVE-2025-66423 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions Tryton trytond 6.0 before 7.6.11 does not enforce access rights for the route of the HTML editor. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.70. O3 Security Β· Impact-Aware SCA ### Is CVE-2025-66423 in your dependencies? Find it across PyPI, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)