Skip to main content
Menu
CVEs

Pozeiden remote memory corruption in grid-layout renderer

Affects Pozeiden 0.2.0 and earlier in the c4, class, er and requirement grid-layout renderers. Fixed in 0.3.0.

CVE-2026-77347Published , updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.3.0
Who is exposed
Not reported

Summary

Pozeiden, a MermaidJS diagram renderer written in Zig from sc2in, contains out-of-bounds read and write flaws that a remote attacker can trigger without logging in, using a valid diagram with many grid items or deep nesting. The result is a crash that denies service in safe builds, and stack memory corruption in ReleaseSmall WASM builds.

Written by a model

Original description

Pozeiden is a MermaidJS renderer written in Zig. Prior to 0.3.0, src/renderers/c4.zig, src/renderers/class.zig, src/renderers/er.zig, and src/renderers/requirement.zig use fixed row-layout arrays while deriving subsequent loop bounds from an untrusted diagram's actual item count, and src/renderers/state.zig indexes a fixed depth array using user-controlled nesting depth. A valid diagram with at least 193 grid items can make the row count exceed the 64-row storage, while a deeply nested state diagram can exceed the col_count depth storage through the public pozeiden.render() path. Safe CLI and ReleaseSafe builds abort the rendering process, enabling reliable denial of service in applications that render untrusted diagrams. ReleaseSmall WASM builds with safety checks disabled instead perform out-of-bounds stack reads or writes, creating a memory-safety violation. This issue is fixed in version 0.3.0.

Who should check

Anyone rendering untrusted Mermaid diagrams with sc2in pozeiden through 0.2.0, including embedders calling pozeiden.render() and WASM builds.

“All versions through 0.2.0 are affected.”

github.com

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-77347 (Pozeiden: Out-of-bounds read/write (crash / memory corruption) on valid diagrams in grid-layout renderers), 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-77347 (entry last updated 2026-11-20):
Affected:
- sc2in pozeiden: fixed in 0.3.0
Fixed versions: 0.3.0.
Conditions (all must be true for the bug to be hit):
- Pozeiden version 0.2.0 or earlier, in the grid-layout renderers (c4, class, er, requirement). (source: https://github.com/sc2in/pozeiden/security/advisories/GHSA-rg4m-w3p2-gf3p)
- A valid diagram declaring at least 193 items in one of the grid-layout renderers. (source: https://github.com/sc2in/pozeiden/security/advisories/GHSA-rg4m-w3p2-gf3p)
- A state diagram with deep user-controlled nesting depth. (source: https://github.com/sc2in/pozeiden/security/advisories/GHSA-rg4m-w3p2-gf3p)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77347 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77347 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-rg4m-w3p2-gf3p
- https://github.com/sc2in/pozeiden/commit/a48c3b11d74e485409644420739a6d61cd395ed3
- 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-77347
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-77347"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · sc2in/pozeiden · Advisory GHSA-rg4m-w3p2-gf3p
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-77347
Other links 2
RepositoryGitHub · sc2in/pozeiden · Commit a48c3b11
RepositoryGitHub · sc2in/pozeiden · Release v0.3.0

Questions about CVE-2026-77347

Is CVE-2026-77347 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

What does this mean?

A valid diagram that declares at least 193 items in a grid-layout renderer can make the renderer write past the end of its row data. In safe builds this aborts the rendering process, and in ReleaseSmall WASM builds it causes out-of-bounds stack reads and writes, which is a memory-safety violation.

Source: github.com

Which versions are affected by CVE-2026-77347?

pozeiden: before 0.3.0.

Source: cve.now feed data

Am I affected, and how do I check?

All Pozeiden versions through 0.2.0 are affected, in the c4, class, er and requirement renderers. The version can be checked with the Pozeiden version command in the environment where diagrams are rendered. Diagrams with 193 or more items in those renderers are the triggering case, and the advisory also names state diagrams with deep nesting.

Source: github.com

How do I fix CVE-2026-77347?

Upgrade Pozeiden to 0.3.0, which is the fixed version listed for this vulnerability.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.