# CVE-2025-66422: trytond allows remote attackers to obtain sensitive trace-back (server setup) information

> Remote attackers can obtain sensitive server setup information via traceback exposure in Tryton trytond, requiring an upgrade to secure the system.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Nov 2025
- **Updated:** 1 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-66422, GHSA-jqfc-9q34-prhg, PYSEC-2026-1990, UBUNTU-CVE-2025-66422

## What is CVE-2025-66422?

CVE-2025-66422 is a medium-severity vulnerability in trytond, published on 30 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-402 (Transmission of Private Resources into a New Sphere)

## Which versions are affected by CVE-2025-66422?

9 open source packages ship an affected version, including trytond. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `trytond` | PyPI | All versions | 6.0.70, 7.0.40, 7.4.21, 7.6.11 |
| `trytond` | PyPI | All versions | 6.0.70 |
| `trytond` | PyPI | All versions | 6.0.70 |
| `trytond` | PyPI | From 7.0.0 | 7.0.40 |
| `trytond` | PyPI | From 7.0.0 | 7.0.40 |
| `trytond` | PyPI | From 7.1.0 | 7.4.21 |
| `trytond` | PyPI | From 7.1.0 | 7.4.21 |
| `trytond` | PyPI | From 7.5.0 | 7.6.11 |
| `trytond` | PyPI | From 7.5.0 | 7.6.11 |

Products: Tryton Trytond.

## How do I fix CVE-2025-66422?

Upgrade trytond to a fixed version for your release line: 6.0.70, 7.0.40, 7.4.21 or 7.6.11.

## Is CVE-2025-66422 being exploited?

There is no known exploitation of CVE-2025-66422 in the wild and no public exploit code.

## Other vulnerabilities in trytond

- [CVE-2012-2238](https://insights.sbomify.com/CVE-2012-2238/): trytond Incorrect Authorization vulnerability (high 7.5)
- [CVE-2025-66423](https://insights.sbomify.com/CVE-2025-66423/): trytond does not enforce access rights for the route of the HTML editor. (high 7.1)
- [CVE-2025-66424](https://insights.sbomify.com/CVE-2025-66424/): trytond does not enforce access rights for data export (medium 6.5)
- [CVE-2012-0215](https://insights.sbomify.com/CVE-2012-0215/): Trytond allows modification of privileges of arbitrary users (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66422 and fix it if it is affected.

What it is: CVE-2025-66422 is a medium-severity vulnerability in trytond, published on 30 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66422 in the wild and no public exploit code.

Affected packages and fixed versions:
- trytond (PyPI): affected all versions; fixed in 6.0.70, 7.0.40, 7.4.21, 7.6.11
- trytond (PyPI): affected all versions; fixed in 6.0.70
- trytond (PyPI): affected all versions; fixed in 6.0.70
- trytond (PyPI): affected from 7.0.0; fixed in 7.0.40
- trytond (PyPI): affected from 7.0.0; fixed in 7.0.40
- trytond (PyPI): affected from 7.1.0; fixed in 7.4.21
- trytond (PyPI): affected from 7.1.0; fixed in 7.4.21
- trytond (PyPI): affected from 7.5.0; fixed in 7.6.11
- trytond (PyPI): affected from 7.5.0; fixed in 7.6.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-66422/ (Markdown: https://insights.sbomify.com/CVE-2025-66422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-66422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-66422
- OSV: https://osv.dev/vulnerability/CVE-2025-66422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-66422/
Summaries are generated and may contain mistakes; the official description above is the record.