SGLang issue 44641: client-defined image hash controls reused multimodal KV cache

Evidence record

Reported cache identity confusion can cause image B to reuse prefix-cache entries belonging to image A in selected native request paths.

Read the original source ↗

Claim-level citations (3)

• supportsSGLang accepts caller-supplied image hash as cache identity in native inference requests: The affected behavior is described for the native generation path and an explicit trust-caller hash mode; it is not established for every API route.

  Affected path and proposed fix

• supportsSGLang accepts caller-supplied image hash as cache identity in native inference requests: The issue author reports that supplying an earlier image cache hash with a different image caused response text to reflect the earlier image context.

  Issue description; reproduction with two image inputs

• supportsSGLang accepts caller-supplied image hash as cache identity in native inference requests: Issue 44641 reports a two-client test where a second client supplied a different image but the earlier client's declared hash and received text derived from the first client's cached image. The reporter also reproduced wrong-image reuse after three cold restarts.

  Issue #44641, reproduction and two-host cross-client check; 3/3 cold restarts