Arbitrary Code Execution in json-ptrGHSA-rrqv-vjrw-hrcr
Fix: 418sec/json-ptr#3GHSA-rrqv-vjrw-hrcr is a remote code execution vulnerability in json-ptr. A fix is available for json-ptr — see the affected versions and patch details below.
Real-World Exposure
json-ptrReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | json-ptr | all versions | 2.1.0npm install json-ptr@2.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json-ptr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update json-ptr to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrqv-vjrw-hrcr 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 GHSA-rrqv-vjrw-hrcr in your dependencies?
Find it across npm, including transitive dependencies.