Vulnerability in jodit (CVE-2026-54756)
Summary
Vulnerability in jodit (CVE-2026-54756). Risk of unauthorized operations or information disclosure. Exploitable via ConfigMerge. Mitigation: upgrade to 4.12.18 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54756 has been found in jodit.
Attackers can target a specific entry point like ConfigMerge over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jodit to 4.12.18 or later.
If unsure, ask your IT team or search "jodit CVE-2026-54756" on the vendor's site.
CVE-2026-54756 (jodit) — CWE-1321
Attack surface: ConfigMerge / ConfigProto / controls / Object.prototype
Patched: 4.12.18 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in jodit. Attackers reach the vulnerable code path via ConfigMerge.
Check the vendor advisory for the affected versions of jodit. Attack surface: ConfigMerge / ConfigProto / controls / Object.prototype.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.12.18.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jodit' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jodit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
joditを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade jodit to 4.12.18ステージング環境で 4.12.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com