How severe is CVE-2016-7037?

CVE-2016-7037 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2016-7037 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-7037?

CVE-2016-7037 affects Emarref Jwt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2016-7037?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-7037 published?

CVE-2016-7037 was published on 2017-01-23 and last updated on 2026-06-17.

CVE-2016-7037

CVE-2016-7037 is a high-severity vulnerability in Emarref Jwt with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-361.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-361
Affected product: Emarref Jwt
Published: 2017-01-23
Last modified: 2026-06-17

Description

The verify function in Encryption/Symmetric.php in Malcolm Fell jwt before 1.0.3 does not use a timing-safe function for hash comparison, which allows attackers to spoof signatures via a timing attack.

Frequently asked questions

What is CVE-2016-7037?: The verify function in Encryption/Symmetric.php in Malcolm Fell jwt before 1.0.3 does not use a timing-safe function for hash comparison, which allows attackers to spoof signatures via a timing attack.
How severe is CVE-2016-7037?: CVE-2016-7037 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2016-7037 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-7037?: CVE-2016-7037 affects Emarref Jwt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-7037?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-7037 published?: CVE-2016-7037 was published on 2017-01-23 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:emarref:jwt:*:*:*:*:*:*:*:*

Other CWE-361 vulnerabilities

CVE-2016-7547 — Critical (CVSS 9.8): A command execution flaw on the Trend Micro Threat Discovery Appliance 2.6.1062r1 exists with the timezone parameter in…
CVE-2016-7036 — Critical (CVSS 9.8): python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time…
CVE-2016-1643 — High (CVSS 8.8): The ImageInputType::ensurePrimaryContent function in WebKit/Source/core/html/forms/ImageInputType.cpp in Blink, as used…
CVE-2015-5300 — High (CVSS 7.5): The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock that was…
CVE-2016-1000345 — Medium (CVSS 5.9): In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle…
CVE-2016-1000341 — Medium (CVSS 5.9): In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack.…

Browse all CWE-361 vulnerabilities →