VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

tryton: vulnerability history, versions and safety

tryton is a package in the PyPI ecosystem. Vulert records 9 vulnerabilities for it across 0 release, from Nov 2013 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H2 U7
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 09 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tryton vulnerabilities

Vulert verdict on tryton 8.2.0 i

Updated on 23 Oct 2026

Good news: 8.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 9.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 8.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.2.0 — unaffected i
  • Vulnerabilities on record 9 over 12 years · 1 in the last year i
  • Latest disclosure 09 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Last release this month i
  • Licence GPL-3.0-or-later i
  • Similar names triton, trytond i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for tryton, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
8.2.0 05 Oct 2026 none GPL-3.0-or-later — Details →
7.0.44 16 Sep 2026 none GPL-3.0 — Details →
7.8.14 16 Sep 2026 none GPL-3.0 — Details →
8.0.9 16 Sep 2026 none GPL-3.0-or-later — Details →
7.0.43 15 Aug 2026 none GPL-3.0 — Details →
7.8.13 15 Aug 2026 none GPL-3.0 — Details →
8.0.8 15 Aug 2026 none GPL-3.0-or-later — Details →
7.0.42 15 Jul 2026 none GPL-3.0 — Details →
7.8.12 15 Jul 2026 none GPL-3.0 — Details →
8.0.7 15 Jul 2026 none GPL-3.0-or-later — Details →
7.0.41 01 Jul 2026 none GPL-3.0 — Details →
7.8.11 01 Jul 2026 none GPL-3.0 — Details →
8.0.6 01 Jul 2026 none GPL-3.0-or-later — Details →
7.0.40 18 Jun 2026 none GPL-3.0 — Details →
7.8.10 18 Jun 2026 none GPL-3.0 — Details →
8.0.5 18 Jun 2026 none GPL-3.0-or-later — Details →
7.0.39 02 Jun 2026 none GPL-3.0 — Details →
7.8.9 02 Jun 2026 none GPL-3.0 — Details →
8.0.4 02 Jun 2026 none GPL-3.0-or-later — Details →
7.0.38 20 May 2026 none GPL-3.0 — Details →
7.8.8 20 May 2026 none GPL-3.0 — Details →
8.0.3 20 May 2026 none GPL-3.0-or-later — Details →
7.0.37 02 May 2026 none GPL-3.0 — Details →
7.6.13 02 May 2026 none GPL-3.0 — Details →
7.8.7 02 May 2026 none GPL-3.0 — Details →
8.0.2 02 May 2026 none GPL-3.0-or-later — Details →
8.0.1 22 Apr 2026 none GPL-3.0-or-later — Details →
8.0.0 20 Apr 2026 none GPL-3.0-or-later — Details →
6.0.62 16 Apr 2026 none GPL-3.0 — Details →
7.0.36 16 Apr 2026 none GPL-3.0 — Details →
7.6.12 16 Apr 2026 none GPL-3.0 — Details →
7.8.6 16 Apr 2026 none GPL-3.0 — Details →
6.0.61 18 Mar 2026 none GPL-3.0 — Details →
7.0.35 18 Mar 2026 none GPL-3.0 — Details →
7.6.11 18 Mar 2026 none GPL-3.0 — Details →
7.8.5 18 Mar 2026 none GPL-3.0 — Details →
6.0.60 02 Mar 2026 none GPL-3.0 — Details →
7.0.34 02 Mar 2026 none GPL-3.0 — Details →
7.6.10 02 Mar 2026 none GPL-3.0 — Details →
7.8.4 02 Mar 2026 none GPL-3.0 — Details →
6.0.59 18 Feb 2026 none GPL-3.0 — Details →
7.0.33 18 Feb 2026 none GPL-3.0 — Details →
7.6.9 18 Feb 2026 none GPL-3.0 — Details →
7.8.3 18 Feb 2026 none GPL-3.0 — Details →
6.0.58 01 Feb 2026 none GPL-3.0 — Details →
7.0.32 01 Feb 2026 none GPL-3.0 — Details →
7.6.8 01 Feb 2026 none GPL-3.0 — Details →
7.8.2 01 Feb 2026 none GPL-3.0 — Details →
7.0.31 20 Dec 2025 none GPL-3.0 — Details →
7.4.15 20 Dec 2025 none GPL-3.0 — Details →
7.6.7 20 Dec 2025 none GPL-3.0 — Details →
7.8.1 20 Dec 2025 none GPL-3.0 — Details →
6.0.57 17 Dec 2025 none GPL-3.0 — Details →
7.0.30 17 Dec 2025 none GPL-3.0 — Details →
7.4.14 17 Dec 2025 none GPL-3.0 — Details →
7.6.6 17 Dec 2025 none GPL-3.0 — Details →
7.8.0 15 Dec 2025 none GPL-3.0 — Details →
6.0.56 21 Nov 2025 none GPL-3.0 — Details →
7.0.29 21 Nov 2025 none GPL-3.0 — Details →
7.4.13 21 Nov 2025 none GPL-3.0 — Details →
7.6.5 21 Nov 2025 none GPL-3.0 — Details →
6.0.55 02 Nov 2025 none GPL-3.0 — Details →
7.0.28 02 Nov 2025 none GPL-3.0 — Details →
7.4.12 02 Nov 2025 none GPL-3.0 — Details →
7.6.4 02 Nov 2025 none GPL-3.0 — Details →
7.6.3 03 Sep 2025 none GPL-3.0 — Details →
6.0.54 04 Jun 2025 none GPL-3.0 — Details →
7.0.27 04 Jun 2025 none GPL-3.0 — Details →
7.2.20 04 Jun 2025 none GPL-3.0 — Details →
7.4.11 04 Jun 2025 none GPL-3.0 — Details →
7.6.2 04 Jun 2025 none GPL-3.0 — Details →
7.0.26 15 May 2025 none GPL-3.0 — Details →
7.2.19 15 May 2025 none GPL-3.0 — Details →
7.4.10 15 May 2025 none GPL-3.0 — Details →
7.6.1 15 May 2025 none GPL-3.0 — Details →
6.0.53 02 May 2025 none GPL-3.0 — Details →
7.0.25 02 May 2025 none GPL-3.0 — Details →
7.2.18 02 May 2025 none GPL-3.0 — Details →
7.4.9 02 May 2025 none GPL-3.0 — Details →
7.6.0 28 Apr 2025 none GPL-3.0 — Details →
6.0.52 26 Apr 2025 none GPL-3.0 — Details →
7.0.24 26 Apr 2025 none GPL-3.0 — Details →
7.2.17 26 Apr 2025 none GPL-3.0 — Details →
7.4.8 26 Apr 2025 none GPL-3.0 — Details →
6.0.51 02 Apr 2025 none GPL-3.0 — Details →
7.0.23 02 Apr 2025 none GPL-3.0 — Details →
7.2.16 02 Apr 2025 none GPL-3.0 — Details →
7.4.7 02 Apr 2025 none GPL-3.0 — Details →
6.0.50 04 Mar 2025 none GPL-3.0 — Details →
7.0.22 04 Mar 2025 none GPL-3.0 — Details →
7.2.15 04 Mar 2025 none GPL-3.0 — Details →
7.4.6 04 Mar 2025 none GPL-3.0 — Details →
6.0.49 16 Feb 2025 none GPL-3.0 — Details →
7.0.21 16 Feb 2025 none GPL-3.0 — Details →
7.2.14 16 Feb 2025 none GPL-3.0 — Details →
7.4.5 16 Feb 2025 none GPL-3.0 — Details →
7.2.13 16 Jan 2025 none GPL-3.0 — Details →
7.4.4 16 Jan 2025 none GPL-3.0 — Details →
6.0.48 01 Jan 2025 none GPL-3.0 — Details →
7.0.20 01 Jan 2025 none GPL-3.0 — Details →
7.2.12 01 Jan 2025 none — — Details →
7.4.3 01 Jan 2025 none — — Details →
6.0.47 16 Dec 2024 none — — Details →
7.0.19 16 Dec 2024 none — — Details →
7.2.11 16 Dec 2024 none — — Details →
7.4.2 16 Dec 2024 none — — Details →
6.0.46 01 Dec 2024 none — — Details →
7.0.18 01 Dec 2024 none — — Details →
7.2.10 01 Dec 2024 none — — Details →
7.4.1 01 Dec 2024 none — — Details →
6.0.45 06 Nov 2024 none — — Details →
7.0.17 06 Nov 2024 none — — Details →
7.2.9 06 Nov 2024 none — — Details →
7.4.0 04 Nov 2024 none — — Details →
6.0.44 18 Oct 2024 none — — Details →
7.0.16 18 Oct 2024 none — — Details →
7.2.8 18 Oct 2024 none — — Details →
7.0.15 05 Oct 2024 none — — Details →
7.2.7 05 Oct 2024 none — — Details →
6.0.43 16 Sep 2024 none — — Details →

The newest 120 of 688 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 1
  • 2016 2
  • 2018 2
  • 2022 3
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tryton

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Arbitrary Command Execution in Tryton 8.8 high 2.4.15 14 May 2022
CVE-2014-6633: Tryton Arbitrary Command Execution Vulnerability 8.8 high 2.4.15 09 Jul 2026
CVE-2022-26662: Tryton Application Platform XML Entity Expansion Vulnerability 7.5 high 5.0.12 10 Mar 2022
CVE-2022-26661: Tryton Application Platform XXE Vulnerability Allows File Access 6.5 medium 5.0.12 10 Mar 2022
CVE-2018-19443: Session Fixation in Tryton 5.9 high 5.0.1 29 Nov 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About tryton

Is tryton safe to use?

Vulert records 9 vulnerabilities for tryton in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 7 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is tryton's Vulert package health score?

Vulert scores tryton 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of tryton affected?

No. 8.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of tryton should I use?

8.2.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does tryton have?

9 vulnerabilities are recorded for tryton in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 7 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tryton vulnerabilities disclosed?

1 vulnerability was recorded for tryton in the last 12 months, and the oldest entry in this database dates to 18 Nov 2013. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tryton are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tryton for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tryton version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.