← Back
CVE-2026-22810
high
CVSS 8.2
Vulnerability in @joplin/onenote-converter (CVE-2026-22810)
Summary
vulnerability in @joplin/onenote-converter (CVE-2026-22810). Successful exploitation can lead to full system takeover. Exploitable via ``embedded_file.rs``. Mitigation: upgrade to `3.5.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-22810** has been found in @joplin/onenote-converter.
Attackers can target a specific entry point like ``embedded_file.rs`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.2/10.
What to do: upgrade @joplin/onenote-converter to **3.5.7** or later.
If unsure, ask your IT team or search "@joplin/onenote-converter CVE-2026-22810" on the vendor's site.
CVE-2026-22810 (@joplin/onenote-converter) — CWE-24 / CVSS v3 8.2
Attack vector: local
Attack surface: `embedded_file.rs` / `determine_filename` / `log.txt`
Patched: `3.5.7` — 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.
❓ What is the problem
**A vulnerability** (CWE-24) exists in @joplin/onenote-converter. Attackers reach the vulnerable code path via ``embedded_file.rs`` without authentication.
📍 Affected scope
@joplin/onenote-converter — . Attack surface: `embedded_file.rs` / `determine_filename` / `log.txt`.
🔥 Severity
Severity: High (CVSS 8.2/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.5.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@joplin/onenote-converter' .` 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 '@joplin/onenote-converter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@joplin/onenote-converter` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @joplin/onenote-converter to 3.5.7ステージング環境で 3.5.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@joplin/onenote-converter
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.5.7"}]}]