Is My Json Valid Project maintains a focused JSON validation tool with a narrow product scope but positioned in the common parsing layer across applications that handle JSON data exchange. The vendor's observed vulnerability signal centers on improper input validation in the JSON parsing mechanism, a structural weakness class typical of schema-validation and data-intake components. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Is My Json Valid Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2016-2537HIGH The is-my-json-valid package before 2.12.4 for Node.js has an incorrect exports['utc-millisec'] regular expression, which allows remote attackers to cause a denial of service (bloc | Feb 23, 2016 | 7.5 | 24 | NO | NO |
CVE-2018-1107MEDIUM 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 | Mar 30, 2021 | 5.3 | 20 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Is My Json Valid Project.
Media articles that mention a CVE ID that affects a product developed by Is My Json Valid Project — matched by CVE ID, not by vendor name.