Host code execution via bypassed binding lookup
Published Aug 21, 2026 · Updated Aug 21, 2026
Code injection in JSONata before 1.8.8 and 2.0.0 through 2.2.0 allows attackers to execute arbitrary host-process code. The src/jsonata.js environment.lookup method calls a binding-controlled hasOwnProperty member instead of an intrinsic ownership check, enabling prototype and constructor access. Applications are exposed only when they evaluate attacker-controlled expressions; successful exploitation runs child processes with the host process privileges.
Summary
What happened
Code injection in JSONata before 1.8.8 and 2.0.0 through 2.2.0 allows attackers to execute arbitrary host-process code. The src/jsonata.js environment.lookup method calls a binding-controlled hasOwnProperty member instead of an intrinsic ownership check, enabling prototype and constructor access. Applications are exposed only when they evaluate attacker-controlled expressions; successful exploitation runs child processes with the host process privileges.
The record
- CVE
- CVE-2026-77414
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- JSONata
- Product
- JSONata
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.8.8
- Affected versionversion=>= 2.0.0, < 2.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-2943-5xfg-gq5f proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo