NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2025-66422 — trytond

MEDIUM

CVE-2025-66422 is a medium-severity (CVSS 4.3) CWE-402 vulnerability in trytond. A fix is available for trytond — see the affected versions and patch details below.

trytond allows remote attackers to obtain sensitive trace-back (server setup) information

Also known asGHSA-jqfc-9q34-prhgPYSEC-2026-1990
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 6, 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-66422.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk
0.00%0.27%0.54%0.81%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from 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 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 Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPItrytond≥ 7.5.0&&< 7.6.117.6.11pip install --upgrade 'trytond==7.6.11'
🐍PyPItrytond≥ 7.1.0&&< 7.4.217.4.21pip install --upgrade 'trytond==7.4.21'
🐍PyPItrytond≥ 7.0.0&&< 7.0.407.0.40pip install --upgrade 'trytond==7.0.40'
🐍PyPItrytondall versions6.0.70pip install --upgrade 'trytond==6.0.70'

Affected Products

1 product · 4 configurations
Application
trytondtryton
≥ 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-66422 is resolved across your whole dependency graph.

  3. 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

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-66422 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-66422: trytond Info Disclosure — Fixed in 7.6.11