Skip to main content

CVE-2026-77347sc2in pozeiden out-of-bounds read

Schedule itHigh8.8EPSS not scored yet

CVE-2026-77347 is a out-of-bounds read in sc2in pozeiden, rated high (8.8 on CVSS 4.0).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Code reads past the end of a buffer, leaking memory contents or crashing. Code writes past the end of a buffer, corrupting memory in ways an attacker can often turn into code execution.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can take it offline. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.

Is it being exploited?

There is no public report of exploitation yet. It can be exploited automatically, at scale.

What to do

  1. Upgrade sc2in pozeiden to 0.3.0 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
  • Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.

Questions to answer about your own systems

  • Where does sc2in pozeiden run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.