Vulnerability in jodit (CVE-2026-55886)
Summary
Vulnerability in jodit (CVE-2026-55886). Risk of unauthorized operations or information disclosure. Exploitable via chain. Mitigation: upgrade to 4.12.26 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. Versions prior to 4.12.26 are vulnerable to Prototype Pollution through Jodit.modules.Helpers.set(chain, value, obj), which walks the dot-separated chain, creating and following each path segment without filtering prototype-mutating keys. A chain that begins with (or contains) proto, constructor, or prototype lets the final assignment reach and mutate Object.prototype. Applications that pass a user-controlled or partially user-controlled key path into Jodit.modules.Helpers.set() could be vulnerable, causing unexpected property injection, logic bypass, denial of service, or secondary security issues. This issue has been fixed in version 4.12.26.
Source: GitHub Security Advisories (Global) 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-55886 has been found in jodit.
Attackers can target a specific entry point like chain over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jodit to 4.12.26 or later.
If unsure, ask your IT team or search "jodit CVE-2026-55886" on the vendor's site.
CVE-2026-55886 (jodit) — CWE-1321
Attack surface: chain / __proto__ / constructor / prototype
Patched: 4.12.26 — 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 chain.
Check the vendor advisory for the affected versions of jodit. Attack surface: chain / __proto__ / constructor / prototype.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.12.26.
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.26ステージング環境で 4.12.26 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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