CVE-2016-10521: jshamcrest is vulnerable to regular expression denial of service (ReDoS) when certain types of user input is p

Q: How do I fix CVE-2016-10521?

jshamcrest: upgrade to newer than 0.7.1. Exact commands for each OS are on this page.

Q: Is CVE-2016-10521 being exploited?

CVE-2016-10521 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-10521 affect?

CVE-2016-10521 affects jshamcrest. Severity is high (CVSS 7.5). jshamcrest is vulnerable to regular expression denial of service (ReDoS) when certain types of user input is passed in to the emailAddress validator.

Q: How urgent is CVE-2016-10521?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2016-10521 is a high-severity flaw (CVSS 7.5) affecting jshamcrest. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-400, CWE-20
Published	2018-05-31
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: jshamcrest project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-05-31 20:29 UTCPublished CVE record published
2026-06-17 00:39 UTCUpdated Record last modified

jshamcrest project jshamcrest UPGRADE

Affected: >= 0.6.7 and <= 0.7.1

Fixed in: newer than 0.7.1

Safe to downgrade to: a release before 0.6.7

1. Check installed version

npm ls jshamcrest

2. UPGRADE to newer than 0.7.1

npm install jshamcrest@">0.7.1"

3. If no update is available yet, DOWNGRADE to a release before 0.6.7

npm view jshamcrest versions npm install jshamcrest@"<0.6.7"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10521?

jshamcrest: upgrade to newer than 0.7.1. Exact commands for each OS are on this page.

Is CVE-2016-10521 being exploited?

CVE-2016-10521 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10521 affect?

CVE-2016-10521 affects jshamcrest. Severity is high (CVSS 7.5). jshamcrest is vulnerable to regular expression denial of service (ReDoS) when certain types of user input is passed in to the emailAddress validator.

How urgent is CVE-2016-10521?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs