CVE-2021-3918

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 3.6%, top 12% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation4% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
4%
EPSS %ILE
89%
KEV
Not listed

Published

November 13, 2021

Last Modified

January 17, 2025

Advisory Details (4)

Auto-updated Sep 4, 2026
Patch available. Sources: github_commit.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20250117-0004/
generic Patch Available

[SECURITY] [DLA 3228-1] node-json-schema security update

https://lists.debian.org/debian-lts-announce/2022/12/msg00013.html
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/bb6ccd63-f505-4e3a-b55f-cd2662c261a9
github_commit

commit 22f146111f54 (kriszyp/json-schema)

Fix landed in kriszyp/json-schema commit 22f146111f54 — awaiting tagged release

https://github.com/kriszyp/json-schema/commit/22f146111f541d9737e832823699ad3528ca7741

Vendor Advisories for CVE-2021-3918(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunode-json-schema (0.2.3-1+deb10u1build0.18.04.1) @ bionic2026-05-26ubuntu
redhatnodejs:12-8040020220523155137.522a0ee42022-07-19redhat
redhatnodejs:12-8020020220523154454.4cda2c842022-06-28redhat
redhatnodejs:12-8060020220523160029.ad008a3a2022-06-21redhat
redhatrhacm2/search-api-rhel8:v2.5.0-252022-06-09redhat
redhatnodejs:12-8010020220518102644.c27ad7f82022-06-07redhat
redhatrh-nodejs12-nodejs-0:12.22.12-2.el72022-06-06redhat
redhatnodejs:14-8050020211213115342.c53685002022-02-01redhat
redhatnodejs:14-8040020211213111158.522a0ee42022-01-25redhat
redhatrh-nodejs14-nodejs-nodemon-0:2.0.3-6.el72022-01-06redhat
redhatnodejs:16-8050020211206113934.c53685002021-12-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
node-json-schema0.2.3-10.2.3-1+deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-json-schema0.3.0+~7.0.6-10.3.0+~7.0.6-1+deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-json-schema—0.4.0+~7.0.9-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-json-schema—0.4.0+~7.0.9-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-json-schema—0.4.0+~7.0.9-1—
npm(1)
PackageVulnerable rangeFixed inDependents
json-schema—0.4.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-09-07 15:58 UTCEPSS rescore
  2. 2026-09-06 13:45 UTCEPSS rescore
  3. 2026-09-06 03:00 UTCOSV refresh
  4. 2026-09-05 15:25 UTCEPSS rescore
  5. 2026-09-04 13:57 UTCEPSS rescore
  6. 2026-09-04 05:03 UTCEPSS rescore
  7. 2026-09-02 14:09 UTCEPSS rescore
  8. 2026-09-01 13:50 UTCEPSS rescore
  9. 2026-09-01 03:33 UTCEPSS rescore
  10. 2026-08-30 19:14 UTCEPSS rescore
  11. 2026-08-30 19:14 UTCEPSS rescore
  12. 2026-08-30 01:19 UTCEPSS rescore
  13. 2026-08-28 21:37 UTCEPSS rescore
  14. 2026-08-27 14:22 UTCEPSS rescore
  15. 2026-08-26 14:43 UTCEPSS rescore
  16. 2026-08-25 13:46 UTCEPSS rescore
  17. 2026-08-24 14:13 UTCEPSS rescore
  18. 2026-08-23 00:16 UTCEPSS rescore
  19. 2026-08-21 23:46 UTCEPSS rescore
  20. 2026-08-20 22:52 UTCEPSS rescore
  21. 2026-08-20 22:52 UTCEPSS rescore
  22. 2026-08-19 17:01 UTCEPSS rescore
  23. 2026-08-19 14:29 UTCOSV refresh
  24. 2026-08-18 13:45 UTCEPSS rescore
  25. 2026-08-17 13:44 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 14:53 UTCEPSS rescore
  2. 2026-08-16 02:11 UTCEPSS rescore
  3. 2026-08-15 01:27 UTCEPSS rescore
  4. 2026-08-13 21:57 UTCEPSS rescore
  5. 2026-08-12 13:48 UTCEPSS rescore
  6. 2026-08-11 13:38 UTCEPSS rescore
  7. 2026-08-09 13:44 UTCEPSS rescore
  8. 2026-08-08 16:33 UTCEPSS rescore
  9. 2026-08-07 16:24 UTCEPSS rescore
  10. 2026-08-06 13:44 UTCEPSS rescore
  11. 2026-08-05 19:14 UTCEPSS rescore
  12. 2026-08-04 10:34 UTCEPSS rescore
  13. 2026-08-04 10:27 UTCOSV refresh
  14. 2026-08-03 10:33 UTCEPSS rescore
  15. 2026-08-02 02:24 UTCEPSS rescore
  16. 2026-08-01 04:13 UTCEPSS rescore
  17. 2026-07-30 16:25 UTCEPSS rescore
  18. 2026-07-30 01:28 UTCEPSS rescore
  19. 2026-07-28 15:33 UTCEPSS rescore
  20. 2026-07-26 14:52 UTCEPSS rescore
  21. 2026-07-26 14:52 UTCEPSS rescore
  22. 2026-07-25 14:15 UTCEPSS rescore
  23. 2026-07-24 14:15 UTCEPSS rescore
  24. 2026-07-23 14:16 UTCEPSS rescore
  25. 2026-07-23 02:03 UTCEG score recompute
  26. 2026-07-22 22:50 UTCEG score recompute
  27. 2026-07-22 14:06 UTCEPSS rescore
  28. 2026-07-21 15:22 UTCEPSS rescore
  29. 2026-07-21 15:22 UTCEPSS rescore
  30. 2026-07-20 17:05 UTCEPSS rescore
  31. 2026-07-19 14:29 UTCEPSS rescore
  32. 2026-07-19 02:27 UTCEPSS rescore
  33. 2026-07-18 10:02 UTCEPSS rescore
  34. 2026-07-18 10:02 UTCEPSS rescore
  35. 2026-07-18 07:59 UTCOSV refresh
  36. 2026-07-16 17:00 UTCEPSS rescore
  37. 2026-07-16 17:00 UTCEPSS rescore
  38. 2026-07-15 16:55 UTCEPSS rescore
  39. 2026-07-15 16:55 UTCEPSS rescore
  40. 2026-07-15 01:58 UTCEPSS rescore
  41. 2026-07-13 22:27 UTCEPSS rescore
  42. 2026-07-13 22:27 UTCEPSS rescore
  43. 2026-07-13 06:11 UTCEPSS rescore
  44. 2026-07-13 06:11 UTCEPSS rescore
  45. 2026-07-12 05:44 UTCEPSS rescore
  46. 2026-07-11 08:25 UTCEPSS rescore
  47. 2026-07-11 08:25 UTCEPSS rescore
  48. 2026-07-09 19:07 UTCEPSS rescore
  49. 2026-07-08 15:12 UTCEPSS rescore
  50. 2026-07-06 16:25 UTCEPSS rescore
  51. 2026-07-06 16:25 UTCEPSS rescore
  52. 2026-07-06 02:21 UTCEPSS rescore
  53. 2026-07-06 02:21 UTCEPSS rescore
  54. 2026-07-05 02:28 UTCEPSS rescore
  55. 2026-07-05 02:28 UTCEPSS rescore
  56. 2026-07-04 06:29 UTCEPSS rescore
  57. 2026-07-04 06:29 UTCEPSS rescore
  58. 2026-07-02 16:57 UTCEPSS rescore
  59. 2026-07-01 15:04 UTCEPSS rescore
  60. 2026-06-30 23:20 UTCEPSS rescore
  61. 2026-06-30 23:20 UTCEPSS rescore
  62. 2026-06-30 06:00 UTCOSV refresh
  63. 2026-06-29 14:04 UTCEPSS rescore
  64. 2026-06-28 14:05 UTCEPSS rescore
  65. 2026-06-28 04:54 UTCEPSS rescore
  66. 2026-06-28 04:54 UTCEPSS rescore
  67. 2026-06-27 03:06 UTCEPSS rescore
  68. 2026-06-27 03:06 UTCEPSS rescore
  69. 2026-06-25 13:48 UTCEPSS rescore
  70. 2026-06-25 13:48 UTCEPSS rescore
  71. 2026-06-24 14:03 UTCEPSS rescore
  72. 2026-06-24 14:03 UTCEPSS rescore
  73. 2026-06-23 21:31 UTCEPSS rescore
  74. 2026-06-23 21:31 UTCEPSS rescore
  75. 2026-06-22 14:24 UTCEPSS rescore

Frequently asked(5)

What is CVE-2021-3918?
CVE-2021-3918 is a critical vulnerability published on November 13, 2021. json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
When was CVE-2021-3918 disclosed?
CVE-2021-3918 was first published in the National Vulnerability Database on November 13, 2021, with the most recent update on January 17, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-3918 actively exploited?
CVE-2021-3918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 10.6% of all scored CVEs.
What is the CVSS score of CVE-2021-3918?
CVE-2021-3918 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2021-3918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-3918, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-3918

Explore →

Is Your Infrastructure Affected by CVE-2021-3918?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs