jsonata Security Analysis
jsonata has 4 known security vulnerabilities in npm (Node.js). Upgrade to version 2.2.1 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 2.2.1
Upgrading to 2.2.1 or later resolves all 4 known vulnerabilities in jsonata. Run: npm install jsonata@2.2.1
Is jsonata in your project?
Check if you're affected and upgrade to 2.2.1 to stay secure.
Vulnerabilities
4 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-77415 JSONata vulnerable to Arbitrary Code Execution via crafted JSONata expressions | CRITICAL | All versions | 2.2.1, 1.8.8 |
| CVE-2026-77414 JSONata vulnerable to Arbitrary Code Execution via crafted JSONata expressions | CRITICAL | All versions | 2.2.1, 1.8.8 |
| CVE-2026-77413 JSONata: Arbitrary Code Execution via crafted JSONata expressions | CRITICAL | All versions | 1.8.8, 2.2.0 |
| CVE-2024-27307 JSONata expression can pollute the "Object" prototype | CRITICAL | All versions | 1.8.7, 2.0.4 |
About This Data
Vulnerability data for jsonata is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related npm (Node.js) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of jsonata.