Quick answers
- Is CVE-2026-77414 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77414 being exploited in the wild.
- How severe is CVE-2026-77414?
- Critical severity, with a CVSS score of 4, published 21 August 2026.
- Which products and versions are affected?
- JSONata All versions before 1.8.8; versions 2.0.0 through 2.2.0.
- Is there a fix for CVE-2026-77414?
- A patch was published on 2026-07-13: Patched in JSONata 2.2.1 and 1.8.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77414 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77414?
- Check whether you run JSONata at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the environment.lookup function's bypassable hasOwnProperty check (CVE-2026-77414, CWE-94: Code Injection). An attacker can craft expressions using prototype pollution techniques—reassigning $hasOwnProperty, $__proto__, and $constructor variables to circumvent security protections—and then execute arbitrary Node.js code via the constructor function. The attack requires no authentication and can be triggered by evaluating any untrusted JSONata expression. The vulnerability was patched in JSONata 2.2.1 and backported to 1.8.8 in PR #799. A working proof-of-concept demonstrates spawning shell commands via process.getBuiltinModule('child_process').execSync().
Affected products
- jsonata-js jsonata >=2.0.0, <2.2.1; <1.8.8
Identifiers
- CVE-2026-77414
- GHSA-2943-5xfg-gq5f
Timeline
- 2026-07-13: disclosed: Advisory published by GitHub
- 2026-07-13: patched: Patched in JSONata 2.2.1 and 1.8.8
- 2026-08-21: advisory: Advisory updated on GitHub