# CVE-2026-77413: JSONata: Arbitrary Code Execution via crafted JSONata expressions

> Attackers can execute arbitrary code by supplying crafted JSONata expressions that exploit prototype pollution in the lookup function.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** CLEANSTART-2026-AP70361, GHSA-8gq3-vp5j-2grp, MINI-4cf8-4rv5-wh6j, MINI-fjxx-xhj4-pqxh, MINI-v6f8-rv6m-xvff

## What is CVE-2026-77413?

CVE-2026-77413 is a critical code injection vulnerability in jsonata-js jsonata, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.0, the src/functions.js lookup function lacked an Object.prototype.hasOwnProperty check and allowed crafted expressions to access inherited prototype members. An attacker able to supply an expression could use inherited prototype setters and getters, constructor access, valueOf, and process.getBuiltinModule to reach the child_process module and execute arbitrary code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.0.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-77413?

4 open source packages ship an affected version, including jsonata.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jsonata` | npm | All versions | 1.8.8 |
| `jsonata` | npm | All versions | 1.8.8 |
| `jsonata` | npm | From 2.0.0 | 2.2.0 |
| `jsonata` | npm | From 2.0.0 | 2.2.0 |

## How do I fix CVE-2026-77413?

Upgrade jsonata to a fixed version for your release line: 1.8.8 or 2.2.0.

## Is CVE-2026-77413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77413 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77413 and fix it if it is affected.

What it is: CVE-2026-77413 is a critical code injection vulnerability in jsonata-js jsonata, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77413 exists.

Affected packages and fixed versions:
- jsonata (npm): affected all versions; fixed in 1.8.8
- jsonata (npm): affected all versions; fixed in 1.8.8
- jsonata (npm): affected from 2.0.0; fixed in 2.2.0
- jsonata (npm): affected from 2.0.0; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77413/ (Markdown: https://insights.sbomify.com/CVE-2026-77413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77413
- OSV: https://osv.dev/vulnerability/CVE-2026-77413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77413/
Summaries are generated and may contain mistakes; the official description above is the record.