CVE-2016-7036 json
python-jose failure to use a constant time comparison for HMAC keys
published 2017-01-23 9 y ago modified 2026-06-17 4 mo ago also GHSA-w799-prg3-cx77 , PYSEC-2017-28 , EUVD-2017-0109
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.
Patch / fix
- pypi python-jose 1.3.2
Exploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | python-jose | <1.3.2 |
1.3.2 |
Classification
References
-
github.com
/mpdavis/python-jose/pull/35/commits/89b46353b9f611e9da38de3d2fedf52331167b93
web, issue-tracking, patch, third-party-advisory
-
github.com
/mpdavis/python-jose/releases/tag/1.3.2
web, issue-tracking, patch, third-party-advisory
-
github.com
/mpdavis/python-jose/commit/73007d6887a7517ac07c6e755e494baee49ef513
web
-
securityfocus.com
/bid/95845
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2016-7036
advisory
-
github.com
/mpdavis/python-jose
package
-
github.com
/pypa/advisory-database/tree/main/vulns/python-jose/PYSEC-2017-28.yaml
web
-
web.archive.org
/web/20210123221523/http://www.securityfocus.com/bid/95845
web
-
github.com
/advisories/GHSA-w799-prg3-cx77
advisory
Sources
- CVE List CVE-2016-7036
- GitHub Advisory GHSA-w799-prg3-cx77
- NVD CVE-2016-7036
- OSV PYSEC-2017-28
Fencer Vulns 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.