🎯 Cache poisoning

The items that name it 7

• Prasenjit Sarkar (@stretchcloud) on X
  threadas classification.key entities2026-10-27
• https://bughunters.google.com/blog/pagebreak-real-world-findings?utm_source=tldrsec.com&utm_medium=newsletter&utm_campaign=tl-dr-sec-348-google-s-pagebreak-scanner-perplexity-s-agent-security-tool-defending-agentically
  writeupas classification.key entities2026-10-01
• [tl;dr sec] #348 - Google's PageBreak Scanner, Perplexity's Agent Security Tool, Defending Agentically
  articleas techniques2026-10-01

  One of three high-severity PageBreak findings in production Google applications

• GitHub Actions Adds cache-mode to Limit Cache Poisoning Risk
  articleas techniques2026-09-16

  Attacker with write access to a cache key that a trusted workflow later reads plants malicious build artifacts or dependencies that execute with that workflow's permissions and secrets

• [tl;dr sec] #341 - Hugging Face Incident Black Hat Talk, CSS Bomb in your Inbox, GitHub Supply Chain Security Improvements
  articleas techniques2026-08-13

  WordPress post cache poisoning used to fabricate oembed_cache rows in the wp2shell chain

• Socket: actions/checkout v7 Blocks Unsafe pull_request_target Checkouts
  articleas classification.key entities2026-06-22
• Securely using pull_request_target - GitHub Enterprise Cloud Docs
  articleas techniques

  Risk where a privileged workflow with write access to shared cache could have its cache entries poisoned to affect unrelated workflow runs