CVE-2021-23807 is a critical-severity (CVSS 9.8) CWE-843 vulnerability in jsonpointer. 2 public exploit references exist, so weaponization risk is real. A fix is available for jsonpointer — see the affected versions and patch details below.
Prototype Pollution in node-jsonpointer
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-23807 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
jsonpointer📦org.webjars.npm:json-pointerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | jsonpointer | all versions | 5.0.0npm install jsonpointer@5.0.0 |
| 📦npm | org.webjars.npm:json-pointer | all versions | 5.0.0npm install org.webjars.npm:json-pointer@5.0.0 |
Affected Products
jsonpointerjanlResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jsonpointer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jsonpointer to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23807 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2021-23807 in your dependencies?
Find it across npm, including transitive dependencies.