Skip to main content
Menu
CVEs

CVE

Kroki Server server-side request forgery in BlockDiag icon attributes

CVE-2026-129485EUVD-2026-126082GHSA-976X-W3HH-23XW

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

6.9MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 0.36.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.36.0.

Published
Last modified
Reference
Last checked
0.31% · 24th percentile
52/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: yes
  • Technical impact: partial

Summary

Kroki before 0.36.0 (by yuzutech) has a server-side request forgery flaw in its BlockDiag engines that can be reached remotely, without logging in, by sending a crafted diagram to the BlockDiag endpoints. An attacker can use it to make the server query internal services or cloud metadata and read local image files.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Kroki before 0.36.0 contains a server-side request forgery vulnerability in the BlockDiag family of engines that allows unauthenticated attackers to make server requests via node icon and background attributes. Attackers can send crafted diagrams to POST /blockdiag/svg or sibling endpoints to query internal services or cloud metadata and read local image files from the server.

cve.now Index

52Pcve.now Index 52 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 57 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.36.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129485 (Kroki before 0.36.0 SSRF via BlockDiag Icon and Background Attributes), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129485 (entry last updated 2026-11-16):
Affected:
- Maven package io.kroki:kroki-server: fixed in 0.36.0
Fixed versions: 0.36.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129485 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129485 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/yuzutech/kroki/security/advisories/GHSA-jwh8-j584-79hp
- https://github.com/yuzutech/kroki/commit/becd3b4a86754cb08d0fe54f65e92a6cab542409
- https://github.com/yuzutech/kroki/releases/tag/v0.36.0
- https://github.com/yuzutech/kroki/blob/v0.35.0/server/src/main/java/io/kroki/server/service/Blockdiag.java#L64-L85
- https://www.vulncheck.com/advisories/kroki-before-0.36.0-ssrf-via-blockdiag-icon-and-background-attributes
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129485
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129485"}.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129485

Is CVE-2026-129485 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129485?

io.kroki:kroki-server (Maven): before 0.36.0.Source: cve.now feed data

How do I fix CVE-2026-129485?

Upgrade to a fixed version: 0.36.0.Source: cve.now feed data