From RuntimeWire · RuntimeWire · · 50s
vLLM fixes Mamba cache bug
vLLM's update prevents 832-token cache errors from producing wrong passcodes.
In brief
vLLM's update prevents 832-token cache errors from producing wrong passcodes. vLLM's November 15th, 2026 fix corrects a Mamba prefix-caching bug that caused 832-token cache hits to generate incorrect passcodes. Originally reported by RuntimeWire.
vLLM fixes Mamba cache bug

vLLM has landed a fix for a Mamba prefix-caching bug that could make a later request resume from a state that had not processed the tokens its cache key claimed it had.
Fix prevents 832-token errors
The fix on vLLM's default branch, dated November 15th, 2026, prevents a block from receiving a full-block hash when the saved Mamba state stops short of the block end.
832-token hit becomes correct
In the contributor's end-to-end reproducer, that distinction changed an 832-token cache hit that produced the wrong passcode into a 16-token hit that produced the correct one.
What matters most
vLLM's November 15th, 2026 fix corrects a Mamba prefix-caching bug that caused 832-token cache hits to generate incorrect passcodes.
Read the TL;DR — this story on one card.





