Cross-Site Scripting in mermaid
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mermaid 8.2.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm mermaid
- Affected
- < 8.2.3
- Fixed in
- 8.2.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-w32g-5hqp-gg6q lists affected ranges: npm mermaid >=0 <8.2.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w32g-5hqp-gg6q lists affected ranges: npm mermaid >=0 <8.2.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Versions of mermaid prior to 8.2.3 are vulnerable to Cross-Site Scripting. If malicious input such as A["<img src=invalid onerror=alert('XSS')</img"] is provided to the application, it will execute the code instead of rendering it as text due to improper output encoding. Recommendation Upgrade to version 8.2.3 or later
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-w32g-5hqp-gg6q
- Revision 1 · created ·
Published from osv record GHSA-w32g-5hqp-gg6q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-w32g-5hqp-gg6q Advisory: Cross-Site Scripting in mermaid IDs: GHSA-w32g-5hqp-gg6q Record: https://patchnext.com/advisories/ghsa-w32g-5hqp-gg6q (revision 2, source checked 26 Oct 2026, 12:09 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mermaid 8.2.3. A vendor fix does not mean a deployment is fixed. ## Affected components - npm mermaid: affected < 8.2.3; fixed in 8.2.3 ## Suggested inspection (read-only) - `npm ls mermaid --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on mermaid. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-w32g-5hqp-gg6q (OSV record GHSA-w32g-5hqp-gg6q lists affected ranges: npm mermaid >=0 <8.2.3 (fixed)) - Verified: https://github.com/advisories/GHSA-w32g-5hqp-gg6q (GitHub-reviewed advisory GHSA-w32g-5hqp-gg6q lists affected ranges: npm mermaid >=0 <8.2.3) Commands are suggestions: review each one before running it.
Loading voting…