Vulnerability in jodit (CVE-2026-65841)
Summary
Vulnerability in jodit (CVE-2026-65841). Risk of unauthorized operations or information disclosure. Exploitable via node.nodeName. Mitigation: upgrade to 4.13.6 or later.
Original description
The description as published by the source.
A element placed directly inside an (or MathML) container was not removed by Jodit's clean-html sanitizer.
The deny/allow tag filter compared node.nodeName against an upper-cased tag hash, but foreign (SVG/MathML) elements preserve their original-case node names — an SVG script reports "script", not "SCRIPT" — so the default denyTags list (which includes script) did not match it. The script therefore survived in the editor value and serialized output, where it could execute when the content was loaded back into a page or editor.
Proof of concept
alert(document.domain);
Load the payload into the editor (e.g. via source mode) and the `` is preserved in editor.value and executes.
Impact
Stored / DOM cross-site scripting. An application that persists editor output and later renders or re-opens it in Jodit can have attacker-supplied script run in a victim's (e.g. an administrator's) authenticated browser context.
Patch
Fixed in 4.13.6: the deny/allow lookup now normalises the tag name to upper case before matching, so a foreign namespace can no longer bypass the filter, while allowTags is still honoured.
Workaround
Upgrade to 4.13.6 or later. Server-side sanitization of stored HTML mitigates in the interim.
Credit
Reported by Roman Kis (@CrownKingClown).
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-65841 has been found in jodit.
Attackers can target a specific entry point like node.nodeName over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jodit to 4.13.6 or later.
If unsure, ask your IT team or search "jodit CVE-2026-65841" on the vendor's site.
CVE-2026-65841 (jodit) — CWE-80
Attack surface: node.nodeName / denyTags / script / editor.value
Patched: 4.13.6 — apply immediately
Workaround: Upgrade to 4.13.6 or later.
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-80) exists in jodit. Attackers reach the vulnerable code path via node.nodeName.
Check the vendor advisory for the affected versions of jodit. Attack surface: node.nodeName / denyTags / script / editor.value.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.13.6.
Workaround: Upgrade to 4.13.6 or later.
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 temporary workaround mitigate
Upgrade to 4.13.6 or later.パッチが適用されるまでの応急処置として、Upgrade to 4.13.6 or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade jodit to 4.13.6ステージング環境で 4.13.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com