← Back
CVE-2026-41150
medium
CVSS 5.3
Vulnerability in mermaid (CVE-2026-41150)
Summary
vulnerability in mermaid (CVE-2026-41150). Risk of unauthorized operations or information disclosure. Exploitable via ``excludes``. Mitigation: upgrade to `10.9.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41150** has been found in mermaid.
Attackers can target a specific entry point like ``excludes`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade mermaid to **10.9.6** or later.
If unsure, ask your IT team or search "mermaid CVE-2026-41150" on the vendor's site.
CVE-2026-41150 (mermaid) — CWE-835 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `excludes` / `mermaid.parse`
Patched: `10.9.6` — apply immediately
Workaround: There are no workarounds available without updating to a newer version of mermaid.
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-835) exists in mermaid. Attackers reach the vulnerable code path via ``excludes`` without authentication.
📍 Affected scope
mermaid — . Attack surface: `excludes` / `mermaid.parse`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **10.9.6**.
🛡️ Workaround
Workaround: There are no workarounds available without updating to a newer version of mermaid.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'mermaid' .` 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 'mermaid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mermaid` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There are no workarounds available without updating to a newer version of mermaid.パッチが適用されるまでの応急処置として、There are no workarounds available without updating to a newer version of mermaid. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade mermaid to 10.9.6ステージング環境で 10.9.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
mermaid
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"10.9.6"}]}]
References
- advisory 134c704f-9b21-4f2e-91b3-4a467353bcc0
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41150
- package https://github.com/mermaid-js/mermaid
- patch security-advisories@github.com
- patch security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web https://github.com/advisories/GHSA-6m6c-36f7-fhxh