Regular Expression Denial of Service in jshamcrest

published 2018-05-31 8y ago modified 2026-06-17 4mo ago also GHSA-xj62-87pg-vcv3 , EUVD-2019-0364

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

jshamcrest is vulnerable to regular expression denial of service (ReDoS) when certain types of user input is passed in to the emailAddress validator.

Is CVE-2016-10521 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	jshamcrest	<=0.7.1	no fix listed

Affected products

HackerOne jshamcrest node module

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption
CWE-20 Improper Input Validation

References

nodesecurity.io /advisories/53
broken-link
nvd.nist.gov /vuln/detail/CVE-2016-10521
advisory
github.com /advisories/GHSA-xj62-87pg-vcv3
advisory
npmjs.com /advisories/53
web

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.