Pozeiden stored XSS in SVG output from diagram rendering
- Exploited
- No known exploitation
- Fix
- Fixed in 0.3.0
- Who is exposed
- Not reported
Summary
Pozeiden, a MermaidJS renderer from sc2in, does not escape attacker-controlled Mermaid values in the SVG it generates. A user with low-level login access can reach this remotely over the network and store SVG that runs script when another user views the published HTML page, which requires that user to take an action.
Written by a model
Original description
Pozeiden is a MermaidJS renderer written in Zig. Prior to 0.3.0, Pozeiden emits attacker-controlled Mermaid values into SVG attributes or markup without sufficient XML escaping or URL scheme validation, and first-party consumers such as zigmark and policypress embed the generated SVG raw into HTML. The click href syntax can introduce a dangerous URL scheme or break out of an attribute; style, classDef, ::: class assignment, and linkStyle color values can inject fill or stroke markup; color and font-weight values can escape text attributes; %%{init}%% themeVariables can inject global renderer attributes; and quadrant y-axis labels can introduce raw markup. These paths involve src/svg/writer.zig, src/renderers/flowchart.zig, src/renderers/quadrant.zig, and src/root.zig. An attacker who can influence rendered Mermaid source can therefore store script-bearing SVG that executes when another user views the published HTML. This issue is fixed in version 0.3.0.
What to do
Upgrade to a fixed version: 0.3.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-77346 (Pozeiden: SVG output injection (stored XSS) via click href, style/classDef colors, %%{init}%% theme variables, and quadrant labels), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-77346 (entry last updated 2026-11-20):
Affected:
- sc2in pozeiden: fixed in 0.3.0
Fixed versions: 0.3.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77346 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77346 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sc2in/pozeiden/security/advisories/GHSA-p2c5-qmq5-3r4f
- https://github.com/sc2in/pozeiden/commit/b11a4cf403ec818e47d8246ed7a034f721cc6ace
- https://github.com/sc2in/pozeiden/releases/tag/v0.3.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-77346
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77346"}.Affected versions
- sc2in pozeidenfixed in 0.3.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · sc2in/pozeiden · Advisory GHSA-p2c5-qmq5-3r4f |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77346 |
| Other links 2 | |
| Repository | GitHub · sc2in/pozeiden · Commit b11a4cf4 |
| Repository | GitHub · sc2in/pozeiden · Release v0.3.0 |
Questions about CVE-2026-77346
Is CVE-2026-77346 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-77346?
pozeiden: before 0.3.0.
Source: cve.now feed data
How do I fix CVE-2026-77346?
Upgrade to a fixed version: 0.3.0.
Source: cve.now feed data
Related
- CVE-2026-77347Pozeiden: Out-of-bounds read/write (crash / memory corruption) on valid diagrams in grid-layout renderers
- CVE-2026-68541PolicyPress: Sensitive content disclosed via CSS-only web redaction and insecure starter workflow defaults
- CVE-2026-94567NukeViet CMS: Stored XSS via SVG upload: the sanitizer is blind to markup hidden inside an internal DTD entity
- CVE-2026-94565NukeViet CMS: Unauthenticated Stored XSS in the Contact module
- CVE-2026-54064NukeViet CMS: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module
- CVE-2026-49259NukeViet: stored XSS through comment reply display names
No corrections so far. Something wrong on this page? Report an error.