python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.
CVE-2016-7036
CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 40% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EPSS
- 79.6%
- KEV
- Not listed
Published
January 23, 2017
Last Modified
May 13, 2026
Advisory Details (3)
Auto-updated May 15, 2026No patch confirmed yet.
generic
Release 1.3.2 · mpdavis/python-jose · GitHub
https://github.com/mpdavis/python-jose/releases/tag/1.3.2generic
fix: Use constant time comparison for HMAC by mpdavis · Pull Request #35 · mpdavis/python-jose · GitHub
https://github.com/mpdavis/python-jose/pull/35/commits/89b46353b9f611e9da38de3d2fedf52331167b93Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-jose | 0.1.0 ... 1.3.1 (27 versions) | 1.3.2 | — |
Frequently asked(5)
What is CVE-2016-7036?
CVE-2016-7036 is a critical vulnerability published on January 23, 2017. python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.
When was CVE-2016-7036 disclosed?
CVE-2016-7036 was first published in the National Vulnerability Database on January 23, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-7036 actively exploited?
CVE-2016-7036 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-7036?
CVE-2016-7036 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-7036?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-7036, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-7036
Is Your Infrastructure Affected by CVE-2016-7036?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.