Re:Poisoning a Go Cache
by lukasschwab on Sunday September 27, 2026 @02:10PM
(#49869222)
Didn't mean to dismiss it. I think it's worth reasoning about! e.g. the CI example — in a build cache shared between ephemeral instances, cache poisoning can smuggle malicious behavior from untrusted environments to trusted ones. You're right.
Didn’t necessarily think you were saying that, but everyone’s looking for an easy excuse with security problems, so best we can do is hit them with the ol' “it depends" :)
Great article, by the way, thank you!
I’m not saying that "a poisoned Go cache" should necessarily be part of everyone’s threat model, but I’d also not just dismiss it by saying "well, it requires disk access". Either might be wrong, depending on your situation.