Public vulnerability disclosure

CVE-2026-102359

Kroki: TikZ Secure Mode Local File Read via LaTeX File I/O Primitives

publishedCWE-22

Kroki creates diagrams from textual descriptions. Prior to 0.31.2, the TikZ backend's tikz/tikz2svg guard used when KROKI_SAFE_MODE is enabled blocks only \verbatiminput while allowing native TeX file-read primitives including \openin, \read, \input, and \include. TeX Live's permissive openin_any setting remains active, so an unauthenticated actor can submit crafted LaTeX to POST /tikz/svg or the generic diagram API and cause the renderer to read any file accessible to the Kroki container user. The file contents are rendered into the returned SVG, which may disclose mounted secrets, configuration data, credentials, private keys, or process environment data. The -no-shell-escape option prevents shell execution but does not restrict these native file operations. This issue is fixed in version 0.31.2.

Technical severity7.5 highCVSS 3.1 · CNA: GitHub_M
Published2026-11-06Source updated 2026-11-11
Collected2026-11-114 attributed sources

Fixes and workarounds

Fix

yuzutech/kroki (other): GitHub reports patched versions 0.31.2. Check the advisory for the affected release branch.

Source: GitHub GHSA-r54f-fq6c-53vw

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
kroki
yuzutech
< 0.31.2 (affected) CNA: GitHub_M
yuzutech/kroki

yuzutech/kroki
other
<= 0.31.1 (affected, GitHub advisory range) GitHub GHSA-r54f-fq6c-53vw

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.5
high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCNA: GitHub_M
3.1 / 7.5
high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NNVD: [email protected]

Exploit evidence

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide