CVE-2025-66422: Medium severity tryton trytond vulnerability
Tryton trytond before 7.6.11 allows remote attackers to obtain sensitive trace-back (server setup) information. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.70.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/trytondto a version that resolves this vulnerability.Fixed in 6.0.70 - Upgrade
Upgrade
pip/trytondto a version that resolves this vulnerability.Fixed in 7.0.40 - Upgrade
Upgrade
pip/trytondto a version that resolves this vulnerability.Fixed in 7.4.21 - Upgrade
Upgrade
pip/trytondto a version that resolves this vulnerability.Fixed in 7.6.11 - Upgrade
Upgrade
tryton/trytondto a version that resolves this vulnerability.Fixed in 7.6.11 - Upgrade
Upgrade
tryton/trytondto a version that resolves this vulnerability.Fixed in 7.4.21 - Upgrade
Upgrade
tryton/trytondto a version that resolves this vulnerability.Fixed in 7.0.40 - Upgrade
Upgrade
tryton/trytondto a version that resolves this vulnerability.Fixed in 6.0.70
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66422?
CVE-2025-66422 is classified as a vulnerability that may expose sensitive information, but no specific severity rating has been assigned.
How do I fix CVE-2025-66422?
To fix CVE-2025-66422, upgrade Tryton trytond to versions 7.6.11, 7.4.21, 7.0.40, or 6.0.70.
What kind of information can be exposed by CVE-2025-66422?
CVE-2025-66422 allows remote attackers to obtain sensitive trace-back information from the server setup.
Which versions of Tryton are affected by CVE-2025-66422?
CVE-2025-66422 affects all versions of Tryton trytond before 7.6.11.
Is there a workaround for CVE-2025-66422?
There is no known workaround for CVE-2025-66422, and it is recommended to upgrade to the fixed versions.