CVE-2026-102359 · Package
NO FIX YET · SEE WHAT TO DO
Kroki turns text into diagrams, and its TikZ renderer blocks only one LaTeX file-read command when safe mode is on. An unauthenticated attacker can submit crafted LaTeX to read any file the Kroki container can access, such as mounted secrets or private keys, and receive the contents inside the returned SVG.
first public Jul 27, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running a self-hosted Kroki server with the TikZ backend reachable by untrusted users, especially with secrets or credentials mounted into the container. Deployments that do not expose the TikZ or generic diagram API to untrusted callers are less exposed, but the sources do not say how far that reduces risk.
Not affected if auth-required, internal-only
Who cares docker, kroki, self-hosted, tikz
0.31.2.POST /tikz/svg reachable from outside your network.KROKI_SAFE_MODE is enabled; the sources say the flaw sits in the safe-mode guard.0.31.2.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.