Skip to content
Fencer Intel
medium 5.3

CVE-2016-1241 json

Tryton allows users to read the hashed password

published 2016-09-07 10 y ago modified 2026-06-17 4 mo ago also GHSA-52j9-v3jc-9xgc , PYSEC-2016-12 , PYSEC-2016-40 , EUVD-2016-0036

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

Tryton 3.x before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allow remote authenticated users to discover user password hashes via unspecified vectors.

Patch / fix

  • pypi trytond 3.2.17, 3.4.14, 3.6.12, 3.8.8, 4.0.4
  • pypi tryton 3.2.17
  • tryton-server Debian 14, Debian 13, Debian 12 4.0.4-1

debian advisories DEBIAN-CVE-2016-1241

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-1241 updated cvss 4.3

tryton: password hashes leak to authenticated users

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N
OSV 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi trytond
>=3.0.0, <3.2.17
>=3.4.0, <3.4.14
>=3.8.0, <3.8.8
>=3.6.0, <3.6.12
>=4.0.0, <4.0.4
<3.2.17
>=3.4, <3.4.14
>=3.6, <3.6.12
>=3.8, <3.8.8
>=4.0, <4.0.4
3.2.17
3.4.14
3.8.8
3.6.12
4.0.4
pypi tryton
<3.2.17
3.2.17

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.