CVE-2018-1107: It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to valid

Q: How do I fix CVE-2018-1107?

is-my-json-valid: upgrade to 1.4.1, 2.17.2. Exact commands for each OS are on this page.

Q: Is CVE-2018-1107 being exploited?

CVE-2018-1107 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-2018-1107 affect?

CVE-2018-1107 affects is-my-json-valid. Severity is medium (CVSS 5.3). It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU t

Q: How urgent is CVE-2018-1107?

Priority 46/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

CVE-2018-1107 is a medium-severity flaw (CVSS 5.3) affecting is-my-json-valid. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Weakness	CWE-400
Published	2021-03-30
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: is-my-json-valid project

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

Am I affected?

Timeline

2021-03-30 02:15 UTCPublished CVE record published
2026-06-17 01:50 UTCUpdated Record last modified

is-my-json-valid project is-my-json-valid UPGRADE

Affected: < 1.4.1 · >= 2.0.0 and < 2.17.2

Fixed in: 1.4.1, 2.17.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls is-my-json-valid

2. UPGRADE to 1.4.1

npm install is-my-json-valid@">=1.4.1"

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

npm view is-my-json-valid versions npm install is-my-json-valid@"<2.0.0"

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-2018-1107?

is-my-json-valid: upgrade to 1.4.1, 2.17.2. Exact commands for each OS are on this page.

Is CVE-2018-1107 being exploited?

CVE-2018-1107 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-2018-1107 affect?

CVE-2018-1107 affects is-my-json-valid. Severity is medium (CVSS 5.3). It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU t

How urgent is CVE-2018-1107?

Priority 46/100. Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs