Vulnerability in vscode-spell-checker (CVE-2026-25931)
Summary
Vulnerability in vscode-spell-checker (CVE-2026-25931). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.5.4 or later.
Original description
The description as published by the source.
vscode-spell-checker is a basic spell checker that works well with code and documents. Prior to v4.5.4, DocumentSettings._determineIsTrusted treats the configuration value cSpell.trustedWorkspace as the authoritative trust flag. The value defaults to true (package.json) and is read from workspace configuration each time settings are fetched. The code coerces any truthy value to true and forwards it to ConfigLoader.setIsTrusted , which in turn allows JavaScript/TypeScript configuration files ( .cspell.config.js/.mjs/.ts , etc.) to be located and executed. Because no VS Code workspace-trust state is consulted, an untrusted workspace can keep the flag true and place a malicious .cspell.config.js ; opening the workspace causes the extension host to execute attacker-controlled Node.js code with the user’s privileges. This vulnerability is fixed in v4.5.4.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-25931 has been found in vscode-spell-checker.
Successful exploitation can lead to full system takeover.
What to do: upgrade vscode-spell-checker to 4.5.4 or later.
If unsure, ask your IT team or search "vscode-spell-checker CVE-2026-25931" on the vendor's site.
CVE-2026-25931 (vscode-spell-checker) — CWE-276
Attack vector: local / unauthenticated
Patched: 4.5.4 — 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-276) exists in vscode-spell-checker.
Check the vendor advisory for the affected versions of vscode-spell-checker.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 4.5.4.
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 'vscode-spell-checker' . 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 'vscode-spell-checker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vscode-spell-checkerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade vscode-spell-checker to 4.5.4ステージング環境で 4.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web drive.google.com
- web github.com