Kroki
Kroki: TikZ Secure Mode Local File Read via LaTeX File I/O Primitives
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.31.2
Fixed in 0.31.2
Mitigation
Upgrade kroki to 0.31.2 or later.
References
- Vendor advisory github.com/yuzutech/kroki/security/advisories/…
- Patch github.com/yuzutech/kroki/commit/9108ab5b429b9…
- Release notes github.com/yuzutech/kroki/releases/tag/v0.31.2
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.