CVSS 3.1
5.0 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NCVE-2026-102356 yuzutech kroki: SSRF
Medium (5.0) in yuzutech kroki. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
Kroki creates diagrams from textual descriptions. From 0.26.0 until 0.31.2, the optional Mermaid companion's mermaid/src/worker.js renders attacker-controlled flowchart image nodes in headless Chromium without a network request policy, even when KROKI_SAFE_MODE is set to secure. An actor who can submit Mermaid source and satisfy any authentication or authorization configured by the deployment can cause the companion to issue HTTP or HTTPS GET requests when requesting PNG output. Exploitation requires the Mermaid companion, PNG rendering through its headless Chromium process, a diagram-submission path available to the actor, and network reachability from the companion to the target. The demonstrated impact is limited to blind request reachability and possible state-changing GET endpoints; response exfiltration, cloud metadata access, port scanning, and access beyond the companion's network reachability are not established. This issue is fixed in version 0.31.2.
Severity
- EPSS
- 0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-14. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-918 Server-Side Request Forgery (SSRF)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-102356 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102356?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102356?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102356 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-102356)
HTML:
<a href="https://cve.bz/cve/CVE-2026-102356"><img src="https://cve.bz/cve/badge/CVE-2026-102356.svg" alt="CVE-2026-102356"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| yuzutech kroki | >= 0.26.0, < 0.31.2 |
Attack patterns (CAPEC)
- CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.