Summary
Arbitrary Code Execution in json-ptr
There is a security vulnerability in json-ptr versions prior to v2.1.0 in which an unscrupulous actor may execute arbitrary code. If your code sends un-sanitized user input to json-ptr's .get() method, your project is vulnerable to this injection-style vulnerability.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-RRQV-VJRW-HRCR? GHSA-RRQV-VJRW-HRCR is a high-severity security vulnerability in json-ptr (npm), affecting versions < 2.1.0. It is fixed in 2.1.0.
- Which versions of json-ptr are affected by GHSA-RRQV-VJRW-HRCR? json-ptr (npm) versions < 2.1.0 is affected.
- Is there a fix for GHSA-RRQV-VJRW-HRCR? Yes. GHSA-RRQV-VJRW-HRCR is fixed in 2.1.0. Upgrade to this version or later.
- Is GHSA-RRQV-VJRW-HRCR exploitable, and should I be worried? Whether GHSA-RRQV-VJRW-HRCR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-RRQV-VJRW-HRCR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-RRQV-VJRW-HRCR? Upgrade
json-ptrto 2.1.0 or later.