# CVE-2026-122234: jsondiffpatch before 0.7.7 XSS via Array-Move Destination in HTML Formatters


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-36c7-f344-vj2m, GHSA-jhmf-rq89-q58p

## What is CVE-2026-122234?

CVE-2026-122234 is a low-severity vulnerability in benjamine jsondiffpatch, published on 4 Nov 2026. 

### Official description

jsondiffpatch before 0.7.7 contains a cross-site scripting vulnerability that allows attackers to inject markup by supplying an unescaped array-move destination index in a delta. Attackers who control a delta passed to formatters.html.format() or formatters.annotated.format() can embed script that executes in the application's origin when output is rendered.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

No fix has been published for CVE-2026-122234 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-122234 being exploited?

There is no known exploitation of CVE-2026-122234 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122234 is a low-severity vulnerability in benjamine jsondiffpatch, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122234 in the wild and no public exploit code.

Affected product: benjamine jsondiffpatch. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-122234/ (Markdown: https://insights.sbomify.com/CVE-2026-122234/index.md)
```

## Sources

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

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