GHSA-39h7-pwv7-rc3x — @excalidraw/excalidraw
GHSA-39h7-pwv7-rc3x is a security vulnerability in @excalidraw/excalidraw. A fix is available for @excalidraw/excalidraw — see the affected versions and patch details below.
Excalidraw vulnerable to XSS via Mermaid sequence diagram labels (KaTeX rendering)
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@excalidraw/excalidrawnpm@excalidraw/mermaid-to-excalidrawnpmDescription
Impact
@excalidraw/[email protected] depends on a Mermaid conversion package version that resolves to a Mermaid release affected by CVE-2025-54881 / GHSA-7rqq-prvp-x9jh. User-supplied Mermaid sequence diagram labels could trigger XSS through Mermaid’s KaTeX label rendering path.
This is patched in @excalidraw/[email protected] by updating @excalidraw/mermaid-to-excalidraw to 2.2.2, which uses a patched Mermaid 11 release.
Moderate severity as this XSS requires manual user action - pasting unsafe Mermaid diagram into the Excalidraw editor. No semi-automated attack vector exists by default (such as accessing a link).
Patches
- Stable
@excalidraw/[email protected]is patched. - Unstable
@excalidraw/excalidraw@nexthas resolved to patched builds since@excalidraw/[email protected]on 2025-08-21. - Direct consumers of
@excalidraw/mermaid-to-excalidrawshould use1.1.3or later.
Workarounds
None.
Resources
- Upstream Mermaid advisory: https://github.com/mermaid-js/mermaid/security/advisories/GHSA-7rqq-prvp-x9jh
- CVE-2025-54881
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @excalidraw/excalidraw | ≥ 0.18.0&&< 0.18.1 | 0.18.1npm install @excalidraw/excalidraw@0.18.1 |
| 📦npm | @excalidraw/mermaid-to-excalidraw | ≥ 0.3.0&&< 1.1.3 | 1.1.3npm install @excalidraw/mermaid-to-excalidraw@1.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @excalidraw/excalidraw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @excalidraw/excalidraw to 0.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-39h7-pwv7-rc3x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-39h7-pwv7-rc3x can be triaged on real exposure rather than presence alone.
Tailored to GHSA-39h7-pwv7-rc3x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-39h7-pwv7-rc3x in your dependencies?
O3 Security finds GHSA-39h7-pwv7-rc3x across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.