← Back
CVE-2026-65841
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-80) exists in jodit. Attackers reach the vulnerable code path via ``node.nodeName`` without authentication.
📍 Affected scope
jodit — . Attack surface: `node.nodeName` / `denyTags` / `script` / `editor.value`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.13.6**.
🛡️ Workaround
Workaround: Upgrade to 4.13.6 or later.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to 4.13.6 or later.パッチが適用されるまでの応急処置として、Upgrade to 4.13.6 or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade jodit to 4.13.6ステージング環境で 4.13.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
jodit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.6"}]}]