# CVE-2026-54756: Jodit Editor: Prototype pollution via Jodit.configure() / ConfigMerge

> Prototype pollution in Jodit Editor allows attackers to modify Object.prototype via user-controlled configuration, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 1 Jul 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-5957-5c94-3v7w

## What is CVE-2026-54756?

CVE-2026-54756 is a medium-severity vulnerability in xdan jodit, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jodit Editor is a WYSIWYG editor with written in pure TypeScript file and image editing capabilities. In versions prior to 4.12.18, Jodit.configure(options) — and the internal ConfigMerge / ConfigProto helpers — merged user-supplied options into the editor configuration without filtering prototype-mutating keys, potentially causing a Prototype Pollution vulnerability. A payload nested under an existing plain-object option such as controls could reach and mutate Object.prototype. Applications that pass user-controlled or partially user-controlled configuration into Jodit.configure() may be vulnerable. This issue was fixed in version 4.12.18.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

2 open source packages ship an affected version, including jodit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jodit` | npm | All versions | 4.12.18 |
| `jodit` | npm | All versions | 4.12.18 |

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

Upgrade jodit to 4.12.18 or later.

## Is CVE-2026-54756 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54756 is a medium-severity vulnerability in xdan jodit, published on 1 Jul 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-54756 exists.

Affected packages and fixed versions:
- jodit (npm): affected all versions; fixed in 4.12.18
- jodit (npm): affected all versions; fixed in 4.12.18

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

## Sources

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

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