How severe is GHSA-jqfc-9q34-prhg?

GHSA-jqfc-9q34-prhg has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jqfc-9q34-prhg?

GHSA-jqfc-9q34-prhg affects the following packages: trytond (PyPI), trytond (PyPI), trytond (PyPI), trytond (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-jqfc-9q34-prhg?

Update trytond to 7.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqfc-9q34-prhg is resolved across your whole dependency graph.

How do I detect GHSA-jqfc-9q34-prhg in my PyPI dependencies?

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.

How do I mitigate GHSA-jqfc-9q34-prhg if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-jqfc-9q34-prhg?

O3 pinpoints whether GHSA-jqfc-9q34-prhg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jqfc-9q34-prhg actively exploited in the wild?

No public exploit code has been indexed for GHSA-jqfc-9q34-prhg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jqfc-9q34-prhg?

GHSA-jqfc-9q34-prhg has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jqfc-9q34-prhg?

GHSA-jqfc-9q34-prhg is classified as CWE-402 (CWE-402). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jqfc-9q34-prhg published, and has it been updated?

GHSA-jqfc-9q34-prhg was published on November 30, 2025 and was last updated on December 2, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-jqfc-9q34-prhg

MEDIUM

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

Also known asCVE-2025-66422

Published

Nov 30, 2025

Updated

Dec 2, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk16th percentile+0.19%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`trytond`	≥ 7.5.0&&< 7.6.11	7.6.11
🐍PyPI	`trytond`	≥ 7.1.0&&< 7.4.21	7.4.21
🐍PyPI	`trytond`	≥ 7.0.0&&< 7.0.40	7.0.40
🐍PyPI	`trytond`	all versions	6.0.70

Detection & mitigation playbook

Open-source dependency

Detect
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 7.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqfc-9q34-prhg 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 GHSA-jqfc-9q34-prhg 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 GHSA-jqfc-9q34-prhg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-jqfc-9q34-prhg in your dependencies?

O3 detects GHSA-jqfc-9q34-prhg across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works